BIZTRAC BETA
Production of electricity from hydropower

BOTNEN KRAFTVERK AS

Org. no. 997832086 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −85,000
Equity NOK −827,000
Incorporated 2012
Share capital NOK 100,000

Signals

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

BOTNEN KRAFTVERK AS is registered as a limited company in Oslo, Oslo with organisation number 997832086. 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 10000 shares. The company's stated purpose is: “Å driva kraftverk ved Botnen i Ullensvåg kommune på ein for eigarane optimal måte. Selskapet skal ikkje driva annan verksemd.”.

Key figures · 2024

Operating profit
NOK −85,000
Equity
NOK −827,000

Financial health · 2024

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

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

Who owns BOTNEN KRAFTVERK AS?

AVENTRON NORWAY AS
BOTNEN KRAFTVERK AS
· NOK −85,000 profit

BOTNEN KRAFTVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOTNEN KRAFTVERK AS

Who owns BOTNEN KRAFTVERK AS?

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

Who is the general manager of BOTNEN KRAFTVERK AS?

Stig-Martin Braate is registered as general manager of BOTNEN KRAFTVERK AS.

Where is BOTNEN KRAFTVERK AS based?

BOTNEN KRAFTVERK 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.