BIZTRAC BETA
Arts creation activities in musical composition

SCENE43 AS

Org. no. 911812258 Limited company (AS) Stavanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK −53,000
Equity NOK 1.7m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−53k kr).

SCENE43 AS is registered as a limited company in Stavanger, Rogaland with organisation number 911812258. The business is classified under arts creation activities in musical composition (NACE 90.112). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av tjenester i tilknytning til underholdnings- og musikkvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK −53,000
Equity
NOK 1.7m
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
4.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.9%
Very good
Equity as a share of total capital

Who owns SCENE43 AS?

CHRISTIAN CABOOM ERIKSEN
SCENE43 AS
NOK 2.1m rev. · NOK −53,000 profit

SCENE43 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SCENE43 AS own?

SCENE43 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SCENE43 AS

Who owns SCENE43 AS?

CHRISTIAN CABOOM ERIKSEN is the largest registered owner, with 50.0%.

What is the revenue of SCENE43 AS?

SCENE43 AS had revenue of NOK 2.1m in 2025.

Who is the general manager of SCENE43 AS?

Randi Tytingvåg is registered as general manager of SCENE43 AS.

Where is SCENE43 AS based?

SCENE43 AS has its business address in Stavanger.

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.