BIZTRAC BETA
Production of electricity from hydropower

HELLEFOSS KRAFT AS

Org. no. 912756734 Limited company (AS) Øvre Eiker Incorporated 1898 Active
Ownership graph ↗
Revenue 2024 NOK 26.0m
Operating profit NOK 479,000
Equity NOK 43.4m
Incorporated 1898
Share capital NOK 2.4m

HELLEFOSS KRAFT AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 912756734. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 1898. Registered share capital is NOK 2.4m, divided into 241000 shares. The company's stated purpose is: “Produksjon og omsetning av energi og annen virksomhet som står i forbindelse med forannevnte formål, herunder drift og forvaltning av selskapets faste eiendommer og øvrige ressurser.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.0m in revenue and NOK 479,000 in operating profit.

Key figures · 2024

Revenue
NOK 26.0m
Operating profit
NOK 479,000
Equity
NOK 43.4m
Est. value
NOK 30.5m

Financial health · 2024

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.7%
Good
Equity as a share of total capital

Who owns HELLEFOSS KRAFT AS?

Å ENERGI VANNKRAFT AS
HELLEFOSS KRAFT AS
NOK 26.0m rev. · NOK 479,000 profit

HELLEFOSS KRAFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELLEFOSS KRAFT AS

Who owns HELLEFOSS KRAFT AS?

Å ENERGI VANNKRAFT AS is the largest registered owner, with 33.4%.

What is the revenue of HELLEFOSS KRAFT AS?

HELLEFOSS KRAFT AS had revenue of NOK 26.0m in 2024.

Who is the general manager of HELLEFOSS KRAFT AS?

Jan Vidar Thoresen is registered as general manager of HELLEFOSS KRAFT AS.

Where is HELLEFOSS KRAFT AS based?

HELLEFOSS KRAFT AS has its business address in Hokksund.

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.