BIZTRAC BETA
Production of electricity from hydropower

VIKAELVA KRAFTVERK AS

Org. no. 992743174 Limited company (AS) Stryn Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 1.6m
Equity NOK −8.3m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−8,3 mill kr).

VIKAELVA KRAFTVERK AS is registered as a limited company in Stryn, Vestland with organisation number 992743174. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000000 shares. The company's stated purpose is: “Utviklling og drift av kraftverk.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 1.6m
Equity
NOK −8.3m
Est. value
NOK 9.3m

Financial health · 2024

Liquidity
6.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-27.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VIKAELVA KRAFTVERK AS?

ENFRAM AS
VIKAELVA KRAFTVERK AS
NOK 3.3m rev. · NOK 1.6m profit

VIKAELVA KRAFTVERK AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKAELVA KRAFTVERK AS

Who owns VIKAELVA KRAFTVERK AS?

ENFRAM AS is the largest registered owner, with 28.9%.

What is the revenue of VIKAELVA KRAFTVERK AS?

VIKAELVA KRAFTVERK AS had revenue of NOK 3.3m in 2024.

Who is the general manager of VIKAELVA KRAFTVERK AS?

Halvard Bøe is registered as general manager of VIKAELVA KRAFTVERK AS.

Where is VIKAELVA KRAFTVERK AS based?

VIKAELVA KRAFTVERK AS has its business address in Stryn.

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.