BIZTRAC BETA
Development of building projects

STORNESVEGEN EIENDOM AS

Org. no. 928602419 Limited company (AS) Kongsberg Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 988,000
Operating profit NOK 685,000
Equity NOK 198,000
Incorporated 2021
Share capital NOK 100,000

STORNESVEGEN EIENDOM AS is registered as a limited company in Kongsberg, Buskerud with organisation number 928602419. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikle, eie og selge hyttetomter og områder, med alt som naturlig hører med, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 988,000 in revenue and NOK 685,000 in operating profit.

Key figures · 2024

Revenue
NOK 988,000
Operating profit
NOK 685,000
Equity
NOK 198,000
Est. value
NOK 821,000

Financial health · 2024

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

Who owns STORNESVEGEN EIENDOM AS?

BLÅNUTEN INVEST AS
STORNESVEGEN EIENDOM AS
NOK 988,000 rev. · NOK 685,000 profit

STORNESVEGEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORNESVEGEN EIENDOM AS

Who owns STORNESVEGEN EIENDOM AS?

BLÅNUTEN INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of STORNESVEGEN EIENDOM AS?

STORNESVEGEN EIENDOM AS had revenue of NOK 988,000 in 2024.

Who is the general manager of STORNESVEGEN EIENDOM AS?

John Helge Stordalen is registered as general manager of STORNESVEGEN EIENDOM AS.

Where is STORNESVEGEN EIENDOM AS based?

STORNESVEGEN EIENDOM AS has its business address in Kongsberg.

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.