BIZTRAC BETA
Other investment companies, except captive companies

OPTIMUM PRIVATE EQUITY 2018 AS

Org. no. 920737455 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −2.0m
Equity NOK 148.9m
Incorporated 2018
Share capital NOK 65,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,0 mill kr).

OPTIMUM PRIVATE EQUITY 2018 AS is registered as a limited company in Oslo, Oslo with organisation number 920737455. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2018. Registered share capital is NOK 65,000, divided into 65000 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder blant annet delta i selskaper med samme formål samt investere i aksjer, andre finansielle instrumenter, fonds- og selskapsandeler, samt annen virksomhet som dertil hører ved.”.

Key figures · 2024

Operating profit
NOK −2.0m
Equity
NOK 148.9m
Est. value
NOK 101.3m

Financial health · 2024

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

Who owns OPTIMUM PRIVATE EQUITY 2018 AS?

TURNSTONE ALTERNATIVE INVESTMENTS AS
OPTIMUM PRIVATE EQUITY 2018 AS
· NOK −2.0m profit

OPTIMUM PRIVATE EQUITY 2018 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OPTIMUM PRIVATE EQUITY 2018 AS own?

OPTIMUM PRIVATE EQUITY 2018 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OPTIMUM PRIVATE EQUITY 2018 AS

Who owns OPTIMUM PRIVATE EQUITY 2018 AS?

TURNSTONE ALTERNATIVE INVESTMENTS AS is the largest registered owner, with 100.0%.

Where is OPTIMUM PRIVATE EQUITY 2018 AS based?

OPTIMUM PRIVATE EQUITY 2018 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.