biztrac. BETA
COMPANY REGISTER PROFILE
928987191 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

STATKRAFT HYDROGEN NORWAY HOLDING AS

Org. no. 928987191 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −10.4m
Equity NOK 77.0m
Incorporated 2022
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10,4 mill kr).

STATKRAFT HYDROGEN NORWAY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 928987191. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 33,000, divided into 3000 shares. The company's stated purpose is: “Eie aksjer eller andeler, direkte eller indirekte, i selskaper som helt eller delvis er tilknyttet Statkraft-konsernet.”.

Former names: NFH 220334 AS

Key figures · 2025

Operating profit
NOK −10.4m
▲ +82 %
Equity
NOK 77.0m
▼ −37 %
Est. value
NOK 90.5m

Financial health · 2025

Liquidity
1.97
Good
Current assets ÷ current liabilities
Profitability
-7.0%
Not satisfactory
Return on total assets
Solidity
65.7%
Very good
Equity as a share of total capital

Who owns STATKRAFT HYDROGEN NORWAY HOLDING AS?

STATKRAFT HYDROGEN NORWAY HOLDING AS
· NOK −10.4m profit

STATKRAFT HYDROGEN NORWAY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STATKRAFT HYDROGEN NORWAY HOLDING AS own?

STATKRAFT HYDROGEN NORWAY HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STATKRAFT HYDROGEN NORWAY HOLDING AS

Who owns STATKRAFT HYDROGEN NORWAY HOLDING AS?

STATKRAFT HYDROGEN HOLDING AS is the largest registered owner, with 100.0%.

Where is STATKRAFT HYDROGEN NORWAY HOLDING AS based?

STATKRAFT HYDROGEN NORWAY HOLDING 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.