BIZTRAC BETA
Other support activities to arts and performing arts

BYKALAS AS

Org. no. 930905801 Limited company (AS) Giske Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 16.1m
Operating profit NOK −83,000
Equity NOK −347,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−347k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−83k kr).

BYKALAS AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 930905801. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapets formål er utvikling og gjennomføring av festival- og kulturarrangementer, samt å eie andeler i tilsvarende selskaper og annet som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.1m in revenue and NOK −83,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.1m
Operating profit
NOK −83,000
Equity
NOK −347,000

Financial health · 2024

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BYKALAS AS?

SKY FESTIVALS AS
BYKALAS AS
NOK 16.1m rev. · NOK −83,000 profit

BYKALAS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYKALAS AS

Who owns BYKALAS AS?

SKY FESTIVALS AS is the largest registered owner, with 40.0%.

What is the revenue of BYKALAS AS?

BYKALAS AS had revenue of NOK 16.1m in 2024.

Where is BYKALAS AS based?

BYKALAS AS has its business address in Giske.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.