BIZTRAC BETA
Manufacture of industrial gases

NH2 NORGE AS

Org. no. 932289598 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK −42,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−42k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

NH2 NORGE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932289598. The business is classified under manufacture of industrial gases (NACE 20.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikle, eie og drive infrastruktur for levering av hydrogen til kunder og annen virksomhet som står i forhold til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK −42,000

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-73.6%
Weak
Equity as a share of total capital

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

Who owns NH2 NORGE AS?

NH2 PRODUCTION AS
NH2 NORGE AS
NOK 0 rev. · NOK −29,000 profit

NH2 NORGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NH2 NORGE AS own?

NH2 NORGE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NH2 NORGE AS

Who owns NH2 NORGE AS?

NH2 PRODUCTION AS is the largest registered owner, with 100.0%.

What is the revenue of NH2 NORGE AS?

NH2 NORGE AS had revenue of NOK 0 in 2025.

Where is NH2 NORGE AS based?

NH2 NORGE AS has its business address in Ålesund.

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.