BIZTRAC BETA
Activities of excursion and event organisers

SKØYEN DESIGNFESTIVAL AS

Org. no. 931155369 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK −104,000
Equity NOK −82,000
Incorporated 2023
Share capital NOK 100,000

Signals

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

SKØYEN DESIGNFESTIVAL AS is registered as a limited company in Oslo, Oslo with organisation number 931155369. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Produksjon av alle typer arrangementer og alt somt står i forbindelse med dette, drift av dertil tilhørende lokasjon samt kjøp, salg og deltakelse i selskap med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK −104,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK −104,000
Equity
NOK −82,000

Financial health · 2024

Liquidity
2.16
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-20.3%
Weak
Equity as a share of total capital

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

Who owns SKØYEN DESIGNFESTIVAL AS?

No shareholders are registered for SKØYEN DESIGNFESTIVAL AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SKØYEN DESIGNFESTIVAL AS

What is the revenue of SKØYEN DESIGNFESTIVAL AS?

SKØYEN DESIGNFESTIVAL AS had revenue of NOK 2.8m in 2024.

Where is SKØYEN DESIGNFESTIVAL AS based?

SKØYEN DESIGNFESTIVAL AS has its business address in Oslo.

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.