BIZTRAC BETA
Production of electricity from hydropower

ODEL HYDRO INVEST AS

Org. no. 932875462 Limited company (AS) Nesbyen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −120,000
Equity NOK −129,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−129k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−120k kr).

ODEL HYDRO INVEST AS is registered as a limited company in Nesbyen, Buskerud with organisation number 932875462. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle og bygge små vannkraftverk i Norge, samt å investere i andre selskaper og tilhørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −120,000
Equity
NOK −129,000

Financial health · 2024

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

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

Who owns ODEL HYDRO INVEST AS?

EIFFEL HYDRO NORWAY
ODEL HYDRO INVEST AS
· NOK −120,000 profit

ODEL HYDRO INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ODEL HYDRO INVEST AS own?

ODEL HYDRO INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about ODEL HYDRO INVEST AS

Who owns ODEL HYDRO INVEST AS?

EIFFEL HYDRO NORWAY is the largest registered owner, with 50.0%.

Who is the general manager of ODEL HYDRO INVEST AS?

Andreas Nicolay Wikborg is registered as general manager of ODEL HYDRO INVEST AS.

Where is ODEL HYDRO INVEST AS based?

ODEL HYDRO INVEST AS has its business address in Nesbyen.

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.