biztrac. BETA
COMPANY REGISTER PROFILE
928165116 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

H2 EIENDOMSUTVIKLING AS

Org. no. 928165116 Limited company (AS) Asker Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK −11,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).

H2 EIENDOMSUTVIKLING AS is registered as a limited company in Asker, Akershus with organisation number 928165116. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Former names: NOTAR 071121-21 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
▼ −39794 %
Equity
NOK −11,000
▼ −199 %
Est. value
NOK 9.8m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
-4.9%
Not satisfactory
Return on total assets
Solidity
-2.5%
Weak
Equity as a share of total capital

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

Who owns H2 EIENDOMSUTVIKLING AS?

H2 EIENDOMSUTVIKLING AS
NOK 0 rev. · NOK −22,000 profit

H2 EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about H2 EIENDOMSUTVIKLING AS

Who owns H2 EIENDOMSUTVIKLING AS?

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

What is the revenue of H2 EIENDOMSUTVIKLING AS?

H2 EIENDOMSUTVIKLING AS had revenue of NOK 0 in 2025.

Where is H2 EIENDOMSUTVIKLING AS based?

H2 EIENDOMSUTVIKLING AS has its business address in Vollen.

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.