BIZTRAC BETA
Production of electricity from hydropower

SALHUSELVA KRAFT AS

Org. no. 922643172 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK −888,000
Equity NOK 7.9m
Incorporated 2019
Share capital NOK 7.6m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−888k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SALHUSELVA KRAFT AS is registered as a limited company in Oslo, Oslo with organisation number 922643172. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2019. Registered share capital is NOK 7.6m, divided into 30000 shares. The company's stated purpose is: “Bygge kraftverk og produsere elektrisk kraft, herunder delta i selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK −888,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK −888,000
Equity
NOK 7.9m
Est. value
NOK 6.9m

Financial health · 2024

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

Who owns SALHUSELVA KRAFT AS?

CLEMENS KRAFTVERK AS
SALHUSELVA KRAFT AS
NOK 2.3m rev. · NOK −888,000 profit

SALHUSELVA KRAFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALHUSELVA KRAFT AS

Who owns SALHUSELVA KRAFT AS?

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

What is the revenue of SALHUSELVA KRAFT AS?

SALHUSELVA KRAFT AS had revenue of NOK 2.3m in 2024.

Where is SALHUSELVA KRAFT AS based?

SALHUSELVA 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.