BIZTRAC BETA
Uoppgitt

STORSTRØMMEN AS

Org. no. 928751961 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK −186,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

STORSTRØMMEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928751961. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selv eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK −11,000
Equity
NOK −186,000

Financial health · 2024

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

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

Who owns STORSTRØMMEN AS?

ARNE HARANES
STORSTRØMMEN AS
· NOK −11,000 profit

STORSTRØMMEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STORSTRØMMEN AS own?

STORSTRØMMEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STORSTRØMMEN AS

Who owns STORSTRØMMEN AS?

ARNE HARANES is the largest registered owner, with 90.0%.

Who is the general manager of STORSTRØMMEN AS?

Åge Eriksen is registered as general manager of STORSTRØMMEN AS.

Where is STORSTRØMMEN AS based?

STORSTRØMMEN AS has its business address in Trondheim.

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.