BIZTRAC BETA
Production of electricity from hydropower

SNEFJELLÅKRAFT AS

Org. no. 996170098 Limited company (AS) Narvik Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −413,000
Equity NOK 3.0m
Incorporated 2010
Share capital NOK 8.0m

Signals

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

SNEFJELLÅKRAFT AS is registered as a limited company in Narvik, Nordland with organisation number 996170098. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2010. Registered share capital is NOK 8.0m, divided into 7959 shares. The company's stated purpose is: “Kraftproduksjon i Snefjellå i Rana Kommune samt hva hermed står i forbindelse. Selskapet kan delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −413,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −413,000
Equity
NOK 3.0m
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns SNEFJELLÅKRAFT AS?

AVENTRON NORWAY AS
SNEFJELLÅKRAFT AS
NOK 1.4m rev. · NOK −413,000 profit

SNEFJELLÅKRAFT AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SNEFJELLÅKRAFT AS

Who owns SNEFJELLÅKRAFT AS?

AVENTRON NORWAY AS is the largest registered owner, with 76.0%.

What is the revenue of SNEFJELLÅKRAFT AS?

SNEFJELLÅKRAFT AS had revenue of NOK 1.4m in 2024.

Where is SNEFJELLÅKRAFT AS based?

SNEFJELLÅKRAFT AS has its business address in Narvik.

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.