BIZTRAC BETA
Production of electricity from hydropower

YTRE OPPEDAL KRAFTVERK AS

Org. no. 997295390 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 453,000
Equity NOK 2.0m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

YTRE OPPEDAL KRAFTVERK AS is registered as a limited company in Oslo, Oslo with organisation number 997295390. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Drive kraftverk ved Oppedalselva i Gulen kommune på en for eiernes optimal måte. Selskapet skal ikke drive annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 453,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 453,000
Equity
NOK 2.0m
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
4.60
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.2%
Weak
Equity as a share of total capital

Who owns YTRE OPPEDAL KRAFTVERK AS?

AVENTRON NORWAY AS
YTRE OPPEDAL KRAFTVERK AS
NOK 3.4m rev. · NOK 453,000 profit

YTRE OPPEDAL KRAFTVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YTRE OPPEDAL KRAFTVERK AS

Who owns YTRE OPPEDAL KRAFTVERK AS?

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

What is the revenue of YTRE OPPEDAL KRAFTVERK AS?

YTRE OPPEDAL KRAFTVERK AS had revenue of NOK 3.4m in 2024.

Where is YTRE OPPEDAL KRAFTVERK AS based?

YTRE OPPEDAL 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.