biztrac. BETA
COMPANY REGISTER PROFILE
994701088 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Production of electricity from wind power

KVALHEIM KRAFT DA

Org. no. 994701088 General partnership with shared liability (DA) Sarpsborg Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 20.5m
Operating profit NOK −234,000
Equity NOK 93.7m
Incorporated 2009

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−234k kr).

KVALHEIM KRAFT DA is registered as a general partnership with shared liability in Sarpsborg, Østfold with organisation number 994701088. The business is classified under production of electricity from wind power (NACE 35.122). The company was incorporated in 2009. The company's stated purpose is: “Eie, utvikle, bygge og drive vindparkene Mehuken I og II i Vågsøy kommune samt eventuelle ytterligere vindparker i omkringliggende arealer.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.5m in revenue and NOK −234,000 in operating profit.

Key figures · 2025

Revenue
NOK 20.5m
▲ +8 %
Operating profit
NOK −234,000
▼ −165 %
Equity
NOK 93.7m
▼ −5 %
Est. value
NOK 77.2m

Financial health · 2025

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

Who owns KVALHEIM KRAFT DA?

No shareholders are registered for KVALHEIM KRAFT DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KVALHEIM KRAFT DA

What is the revenue of KVALHEIM KRAFT DA?

KVALHEIM KRAFT DA had revenue of NOK 20.5m in 2025.

Who is the general manager of KVALHEIM KRAFT DA?

Arild Mousten Fjeldahl is registered as general manager of KVALHEIM KRAFT DA.

Where is KVALHEIM KRAFT DA based?

KVALHEIM KRAFT DA has its business address in Grålum.

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.