BIZTRAC BETA
Civil engineering activities

HAAKON HOLDING AS

Org. no. 989241370 Limited company (AS) Kongsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 904,000
Operating profit NOK 283,000
Equity NOK 5.1m
Incorporated 2005
Share capital NOK 750,000

HAAKON HOLDING AS is registered as a limited company in Kongsberg, Buskerud with organisation number 989241370. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2005. Registered share capital is NOK 750,000, divided into 750 shares. The company's stated purpose is: “Bygg og anlegg, utleie av arbeidskraft, investering og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 904,000 in revenue and NOK 283,000 in operating profit.

Key figures · 2024

Revenue
NOK 904,000
Operating profit
NOK 283,000
Equity
NOK 5.1m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns HAAKON HOLDING AS?

HAAKON HEDENSTAD
HAAKON HOLDING AS
NOK 904,000 rev. · NOK 283,000 profit

HAAKON HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAAKON HOLDING AS own?

HAAKON HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAAKON HOLDING AS

Who owns HAAKON HOLDING AS?

HAAKON HEDENSTAD is the largest registered owner, with 100.0%.

What is the revenue of HAAKON HOLDING AS?

HAAKON HOLDING AS had revenue of NOK 904,000 in 2024.

Who is the general manager of HAAKON HOLDING AS?

Haakon Hedenstad is registered as general manager of HAAKON HOLDING AS.

Where is HAAKON HOLDING AS based?

HAAKON HOLDING 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.