BIZTRAC BETA
Production of electricity from hydropower

TROLLVIKELVA KRAFT AS

Org. no. 920804047 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK −262,000
Equity NOK 13.2m
Incorporated 2018
Share capital NOK 10.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−262k kr).

TROLLVIKELVA KRAFT AS is registered as a limited company in Oslo, Oslo with organisation number 920804047. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2018. Registered share capital is NOK 10.0m, divided into 30000 shares. The company's stated purpose is: “Investeringer i kraftverksvirksomhet, herunder i selskaper som driver med slik virksomhet, samt hva herved står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK −262,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK −262,000
Equity
NOK 13.2m
Est. value
NOK 11.1m

Financial health · 2024

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

Who owns TROLLVIKELVA KRAFT AS?

CLEMENS KRAFTVERK AS
TROLLVIKELVA KRAFT AS
NOK 3.2m rev. · NOK −262,000 profit

TROLLVIKELVA KRAFT AS has 2 registered shareholders:

All shareholders and roles →

Group structure

TROLLVIKELVA KRAFT AS er morselskap for 1 datterselskap:

Frequently asked questions about TROLLVIKELVA KRAFT AS

Who owns TROLLVIKELVA KRAFT AS?

CLEMENS KRAFTVERK AS is the largest registered owner, with 89.0%.

What is the revenue of TROLLVIKELVA KRAFT AS?

TROLLVIKELVA KRAFT AS had revenue of NOK 3.2m in 2024.

Where is TROLLVIKELVA KRAFT AS based?

TROLLVIKELVA KRAFT AS has its business address in Oslo.

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.