BIZTRAC BETA
Production of electricity from hydropower

STATKRAFT OFFSHORE WIND AS

Org. no. 930624047 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −41.1m
Equity NOK 386.3m
Incorporated 2022
Share capital NOK 36,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−41,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STATKRAFT OFFSHORE WIND AS is registered as a limited company in Oslo, Oslo with organisation number 930624047. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2022. Registered share capital is NOK 36,000, divided into 3000 shares. The company's stated purpose is: “Eie, direkte eller indirekte, aksjer eller andeler i selskaper som helt eller delvis er tilknyttet Statkraft-konsernet og som driver virksomhet innenfor utvikling, bygging, eierskap, og drift og vedlikehold av vindparker til havs samt drive virksomhet som står i naturlig sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK −41.1m
Equity
NOK 386.3m
Est. value
NOK 424.9m

Financial health · 2024

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

Who owns STATKRAFT OFFSHORE WIND AS?

STATKRAFT ASSET HOLDING AS
STATKRAFT OFFSHORE WIND AS
· NOK −41.1m profit

STATKRAFT OFFSHORE WIND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STATKRAFT OFFSHORE WIND AS

Who owns STATKRAFT OFFSHORE WIND AS?

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

Where is STATKRAFT OFFSHORE WIND AS based?

STATKRAFT OFFSHORE WIND 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 15.06.2026.

Report a problem

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