BIZTRAC BETA
Development of building projects

H2 PROSJEKT AS

Org. no. 996932141 Limited company (AS) Sandefjord Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −81,000
Equity NOK 566,000
Incorporated 2011
Share capital NOK 1.8m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).

H2 PROSJEKT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 996932141. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 1.8m, divided into 1770 shares. The company's stated purpose is: “Drive handel, servicevirsksomhet og konsulenttjenester. Kjøp, utvikling, drift og salg av fast eiendom. Oppføring av bolig og industribygg. Deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −81,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −81,000
Equity
NOK 566,000
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns H2 PROSJEKT AS?

A HAUGEN INVEST AS
H2 PROSJEKT AS
NOK 2.5m rev. · NOK −81,000 profit

H2 PROSJEKT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about H2 PROSJEKT AS

Who owns H2 PROSJEKT AS?

A HAUGEN INVEST AS is the largest registered owner, with 63.0%.

What is the revenue of H2 PROSJEKT AS?

H2 PROSJEKT AS had revenue of NOK 2.5m in 2024.

Who is the general manager of H2 PROSJEKT AS?

Arild Haugen is registered as general manager of H2 PROSJEKT AS.

Where is H2 PROSJEKT AS based?

H2 PROSJEKT AS has its business address in Sandefjord.

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.