BIZTRAC BETA
Production of electricity from hydropower

BRATTABØELVI KRAFT AS

Org. no. 921045417 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −1.2m
Equity NOK 8.2m
Incorporated 2018
Share capital NOK 63,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).
  • Nylig endring 2026-03-26 Adresseendring registrert 2026-03-26.

BRATTABØELVI KRAFT AS is registered as a limited company in Oslo, Oslo with organisation number 921045417. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2018. Registered share capital is NOK 63,000, divided into 210 shares. The company's stated purpose is: “Selskapets virksomhet er utvikling, utbygging og drift av småskala vannkraftverk, herunder salg av vannkraft og alt som hermed står i forbindelse. Deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −1.2m
Equity
NOK 8.2m
Est. value
NOK 9.1m

Financial health · 2024

Liquidity
2.33
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.4%
Satisfactory
Equity as a share of total capital

Who owns BRATTABØELVI KRAFT AS?

LOCUS HYDRO AS
BRATTABØELVI KRAFT AS
NOK 2.5m rev. · NOK −1.2m profit

BRATTABØELVI KRAFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRATTABØELVI KRAFT AS

Who owns BRATTABØELVI KRAFT AS?

LOCUS HYDRO AS is the largest registered owner, with 100.0%.

What is the revenue of BRATTABØELVI KRAFT AS?

BRATTABØELVI KRAFT AS had revenue of NOK 2.5m in 2024.

Where is BRATTABØELVI KRAFT AS based?

BRATTABØELVI 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.