biztrac. BETA
COMPANY REGISTER PROFILE
931008951 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in dramatic arts

SCENESKREKK AS

Org. no. 931008951 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 2.0m
Equity NOK 2.8m
Incorporated 2023
Share capital NOK 30,000

SCENESKREKK AS is registered as a limited company in Oslo, Oslo with organisation number 931008951. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kunstnerisk virksomhet innenfor teater og film og det som står i naturlig forbindelse med dette. Investering i eiendom, verdipapirer, aksjer og dertil tilhørende tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▼ −10 %
Operating profit
NOK 2.0m
▼ −4 %
Equity
NOK 2.8m
▲ +120 %
Est. value
NOK 6.8m

Financial health · 2025

Liquidity
3.49
Very good
Current assets ÷ current liabilities
Profitability
70.3%
Very good
Return on total assets
Solidity
71.3%
Very good
Equity as a share of total capital

Who owns SCENESKREKK AS?

SCENESKREKK AS
NOK 3.2m rev. · NOK 2.0m profit

SCENESKREKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SCENESKREKK AS own?

SCENESKREKK AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SCENESKREKK AS

Who owns SCENESKREKK AS?

Nicolai Cleve Broch is the largest registered owner, with 100.0%.

What is the revenue of SCENESKREKK AS?

SCENESKREKK AS had revenue of NOK 3.2m in 2025.

Where is SCENESKREKK AS based?

SCENESKREKK 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 03.10.2026.

Report a problem

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