BIZTRAC BETA
Production of electricity from hydropower

VÅGEN KRAFT AS

Org. no. 989788892 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK 2.0m
Equity NOK 4.7m
Incorporated 2006
Share capital NOK 2.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VÅGEN KRAFT AS is registered as a limited company in Bergen, Vestland with organisation number 989788892. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2006. Registered share capital is NOK 2.5m, divided into 25000 shares. The company's stated purpose is: “Produksjon og salg av elektrisk kraft. Selskapet kan også engasjere seg i andre foretak med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK 2.0m
Equity
NOK 4.7m
Est. value
NOK 8.2m

Financial health · 2024

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

Who owns VÅGEN KRAFT AS?

NORSK VANNKRAFT AS
VÅGEN KRAFT AS
NOK 5.1m rev. · NOK 2.0m profit

VÅGEN KRAFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VÅGEN KRAFT AS

Who owns VÅGEN KRAFT AS?

NORSK VANNKRAFT AS is the largest registered owner, with 80.0%.

What is the revenue of VÅGEN KRAFT AS?

VÅGEN KRAFT AS had revenue of NOK 5.1m in 2024.

Who is the general manager of VÅGEN KRAFT AS?

Bjørnar Kjeilen Halvorsen is registered as general manager of VÅGEN KRAFT AS.

Where is VÅGEN KRAFT AS based?

VÅGEN KRAFT AS has its business address in Bergen.

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.