BIZTRAC BETA
Rental and operating of own or leased real estate

STORMÅSAN AS

Org. no. 929471539 Limited company (AS) Frogn Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 771,000
Operating profit NOK 208,000
Equity NOK −81,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−81k kr).

STORMÅSAN AS is registered as a limited company in Frogn, Akershus with organisation number 929471539. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forretningsvirksomhet med hovedvekt på kjøp og salg av eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 771,000 in revenue and NOK 208,000 in operating profit.

Key figures · 2024

Revenue
NOK 771,000
Operating profit
NOK 208,000
Equity
NOK −81,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.6%
Weak
Equity as a share of total capital

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

Who owns STORMÅSAN AS?

RIB INVEST AS
STORMÅSAN AS
NOK 771,000 rev. · NOK 208,000 profit

STORMÅSAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORMÅSAN AS

Who owns STORMÅSAN AS?

RIB INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STORMÅSAN AS?

STORMÅSAN AS had revenue of NOK 771,000 in 2024.

Who is the general manager of STORMÅSAN AS?

Roy Halland Hansen is registered as general manager of STORMÅSAN AS.

Where is STORMÅSAN AS based?

STORMÅSAN AS has its business address in Drøbak.

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.