biztrac. BETA
COMPANY REGISTER PROFILE
989976664 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

H-2 NORD EIENDOM AS

Org. no. 989976664 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 316.0m
Incorporated 2006
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−61k kr).

H-2 NORD EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 989976664. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 2.0m, divided into 19954755 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 tillegg kommer annen nærliggende virksomhet.”.

Former names: INVESTORPROSJEKT VII AS, HANDELSEIENDOM II AS

Key figures · 2025

Operating profit
NOK −61,000
▼ −85 %
Equity
NOK 316.0m
▼ −15 %
Est. value
NOK 288.3m

Financial health · 2025

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

Who owns H-2 NORD EIENDOM AS?

H-2 NORD EIENDOM AS
· NOK −61,000 profit

H-2 NORD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does H-2 NORD EIENDOM AS own?

H-2 NORD EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about H-2 NORD EIENDOM AS

Who owns H-2 NORD EIENDOM AS?

H-2 EIENDOM AS is the largest registered owner, with 100.0%.

Where is H-2 NORD EIENDOM AS based?

H-2 NORD 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.