BIZTRAC BETA
Rental and operating of own or leased real estate

STORMÅSAN 12 AS

Org. no. 921557531 Limited company (AS) Vestby Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 1.5m
Equity NOK 55,000
Incorporated 2018
Share capital NOK 30,000

STORMÅSAN 12 AS is registered as a limited company in Vestby, Akershus with organisation number 921557531. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom og alt som står naturlig i forbindelse med dette, herunder direkte og indirekte investering i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 1.5m
Equity
NOK 55,000
Est. value
NOK 776,000

Financial health · 2024

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

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

Who owns STORMÅSAN 12 AS?

DENTSOLUTION AS
STORMÅSAN 12 AS
NOK 2.4m rev. · NOK 1.5m profit

STORMÅSAN 12 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORMÅSAN 12 AS

Who owns STORMÅSAN 12 AS?

DENTSOLUTION AS is the largest registered owner, with 75.0%.

What is the revenue of STORMÅSAN 12 AS?

STORMÅSAN 12 AS had revenue of NOK 2.4m in 2024.

Who is the general manager of STORMÅSAN 12 AS?

Jack Andre Reisæther Arntzen is registered as general manager of STORMÅSAN 12 AS.

Where is STORMÅSAN 12 AS based?

STORMÅSAN 12 AS has its business address in Vestby.

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.