biztrac. BETA
COMPANY REGISTER PROFILE
922177619 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Trade of electricity

RESERVOIR HOLDING AS

Org. no. 922177619 Limited company (AS) Skien Incorporated 2019 Active
Operating profit NOK −220,000
Equity NOK 221.9m
Incorporated 2019
Share capital NOK 5.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−220k kr).

RESERVOIR HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 922177619. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 2019. Registered share capital is NOK 5.0m, divided into 248316680 shares. The company's stated purpose is: “Eie aksjer, samt gjøre investeringer i virksomhet av enhver art og alt hva som står i forbindelse med dette.”.

Former names: EUFEMIA 2019 VII AS, HYDRO HOLDING AS

Key figures · 2025

Operating profit
NOK −220,000
▼ −1 %
Equity
NOK 221.9m
▼ −1 %
Est. value
NOK 244.1m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
3.2%
Weak
Return on total assets
Solidity
35.0%
Good
Equity as a share of total capital

Who owns RESERVOIR HOLDING AS?

SWISS LIFE GIO II EUR HOLDING S.A.R LU
COLOGNE ALTERNATIVE ASSETS SCA, SIC LU
RESERVOIR HOLDING AS
· NOK −220,000 profit

RESERVOIR HOLDING AS has 2 registered shareholders:

  • SWISS LIFE GIO II EUR HOLDING S.A.R 50.0%
  • COLOGNE ALTERNATIVE ASSETS SCA, SIC 50.0%
All shareholders and roles →

Which companies does RESERVOIR HOLDING AS own?

RESERVOIR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RESERVOIR HOLDING AS

Who owns RESERVOIR HOLDING AS?

SWISS LIFE GIO II EUR HOLDING S.A.R is the largest registered owner, with 50.0%.

Where is RESERVOIR HOLDING AS based?

RESERVOIR HOLDING AS has its business address in Skien.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.