BIZTRAC BETA
Development of building projects

ERIK HAGEN HOLDING AS

Org. no. 927968215 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 33,000
Operating profit NOK 24,000
Equity NOK −1.1m
Incorporated 2021
Share capital NOK 30,000

Signals

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

ERIK HAGEN HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927968215. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 33,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2024

Revenue
NOK 33,000
Operating profit
NOK 24,000
Equity
NOK −1.1m
Est. value
NOK 164,000

Financial health · 2024

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

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

Who owns ERIK HAGEN HOLDING AS?

ERIK HAGEN
ERIK HAGEN HOLDING AS
NOK 33,000 rev. · NOK 24,000 profit

ERIK HAGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERIK HAGEN HOLDING AS own?

ERIK HAGEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ERIK HAGEN HOLDING AS

Who owns ERIK HAGEN HOLDING AS?

ERIK HAGEN is the largest registered owner, with 100.0%.

What is the revenue of ERIK HAGEN HOLDING AS?

ERIK HAGEN HOLDING AS had revenue of NOK 33,000 in 2024.

Where is ERIK HAGEN HOLDING AS based?

ERIK HAGEN HOLDING 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.