BIZTRAC BETA
Production of electricity from hydropower

RØELVA KRAFT AS

Org. no. 999242855 Limited company (AS) Fjord Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −332,000
Incorporated 2012
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−332k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RØELVA KRAFT AS is registered as a limited company in Fjord, Møre og Romsdal with organisation number 999242855. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og omsetning av energi.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −332,000

Financial health · 2024

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-320.4%
Weak
Equity as a share of total capital

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

Who owns RØELVA KRAFT AS?

TAFJORD KRAFTPRODUKSJON AS
RØELVA KRAFT AS
NOK 0 rev. · NOK 0 profit

RØELVA KRAFT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RØELVA KRAFT AS er morselskap for 9 datterselskaper:

Frequently asked questions about RØELVA KRAFT AS

Who owns RØELVA KRAFT AS?

TAFJORD KRAFTPRODUKSJON AS is the largest registered owner, with 100.0%.

What is the revenue of RØELVA KRAFT AS?

RØELVA KRAFT AS had revenue of NOK 0 in 2024.

Where is RØELVA KRAFT AS based?

RØELVA KRAFT AS has its business address in Stordal.

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.