BIZTRAC BETA
Operation of arts facilities and sites

ALADDIN SCENE AS

Org. no. 928493024 Limited company (AS) Halden Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −392,000
Equity NOK −827,000
Incorporated 2021
Share capital NOK 152,000

Signals

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

ALADDIN SCENE AS is registered as a limited company in Halden, Østfold with organisation number 928493024. The business is classified under operation of arts facilities and sites (NACE 90.310). The company was incorporated in 2021. Registered share capital is NOK 152,000, divided into 1520 shares. The company's stated purpose is: “Drive kulturscene og serveringssted.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −392,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −392,000
Equity
NOK −827,000

Financial health · 2024

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

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

Who owns ALADDIN SCENE AS?

HELGE WESTBYE
ALADDIN SCENE AS
NOK 1.7m rev. · NOK −392,000 profit

ALADDIN SCENE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALADDIN SCENE AS

Who owns ALADDIN SCENE AS?

HELGE WESTBYE is the largest registered owner, with 65.8%.

What is the revenue of ALADDIN SCENE AS?

ALADDIN SCENE AS had revenue of NOK 1.7m in 2024.

Who is the general manager of ALADDIN SCENE AS?

Dag Sigmund Johansen is registered as general manager of ALADDIN SCENE AS.

Where is ALADDIN SCENE AS based?

ALADDIN SCENE AS has its business address in Halden.

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.