BIZTRAC BETA
Production of electricity from hydropower

VALEN KRAFTVERK AS

Org. no. 985383820 Limited company (AS) Kvinnherad Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 14.8m
Operating profit NOK 10.1m
Equity NOK 61.9m
Incorporated 2003
Share capital NOK 7.0m

VALEN KRAFTVERK AS is registered as a limited company in Kvinnherad, Vestland with organisation number 985383820. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2003. Registered share capital is NOK 7.0m, divided into 10000 shares. The company's stated purpose is: “Driva produksjon og omsetning av energi samt anna verksemd knytta til desse områda, herunder deltaking i andre verksemder med liknande føremål.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.8m in revenue and NOK 10.1m in operating profit.

Key figures · 2024

Revenue
NOK 14.8m
Operating profit
NOK 10.1m
Equity
NOK 61.9m
Est. value
NOK 68.8m

Financial health · 2024

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

Who owns VALEN KRAFTVERK AS?

VESTLAND FYLKESKOMMUNE ORGANISASJON OG ØKONOMI BERGEN
VALEN KRAFTVERK AS
NOK 14.8m rev. · NOK 10.1m profit

VALEN KRAFTVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VALEN KRAFTVERK AS

Who owns VALEN KRAFTVERK AS?

VESTLAND FYLKESKOMMUNE ORGANISASJON OG ØKONOMI BERGEN is the largest registered owner, with 100.0%.

What is the revenue of VALEN KRAFTVERK AS?

VALEN KRAFTVERK AS had revenue of NOK 14.8m in 2024.

Who is the general manager of VALEN KRAFTVERK AS?

Øyvind Lernes is registered as general manager of VALEN KRAFTVERK AS.

Where is VALEN KRAFTVERK AS based?

VALEN KRAFTVERK AS has its business address in Rosendal.

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.