BIZTRAC BETA
Rental and operating of own or leased real estate

H-2 EIENDOM AS

Org. no. 991835423 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 134.9m
Operating profit NOK 119.6m
Equity NOK 824.6m
Incorporated 2007
Employees 7
Share capital NOK 100,000

H-2 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 991835423. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift, kjøp, og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tilleggg kommer annnen nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 134.9m in revenue and NOK 119.6m in operating profit.

Key figures · 2024

Revenue
NOK 134.9m
Operating profit
NOK 119.6m
Equity
NOK 824.6m
Est. value
NOK 769.0m

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns H-2 EIENDOM AS?

RAGDE EIENDOM AS
H-2 EIENDOM AS
NOK 134.9m rev. · NOK 119.6m profit

H-2 EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does H-2 EIENDOM AS own?

H-2 EIENDOM AS holds stakes in 42 companies:

See the full ownership structure →

Frequently asked questions about H-2 EIENDOM AS

Who owns H-2 EIENDOM AS?

RAGDE EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of H-2 EIENDOM AS?

H-2 EIENDOM AS had revenue of NOK 134.9m in 2024.

Where is H-2 EIENDOM AS based?

H-2 EIENDOM AS has its business address in Oslo.

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.