BIZTRAC BETA
Uoppgitt

EXPLORE CAPITAL II AS

Org. no. 926705679 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −81,000
Equity NOK 7.1m
Incorporated 2021
Share capital NOK 95,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).
  • Nylig endring 2026-02-03 Aksjekapital registrert 2026-02-03.

EXPLORE CAPITAL II AS is registered as a limited company in Oslo, Oslo with organisation number 926705679. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 95,000, divided into 4130000 shares. The company's stated purpose is: “Etablere et fond, og selskapet skal herunder stå ansvarlig for alle kostnader og for øvrig påta seg all annen risiko ved slik mulig etablering, samt å investere, direkte eller indirekte, i det fond som etableres, og potensielt yte tjenester relatert til slikt fond, og å investere i slike aksjer, selskapsandeler, lån og andre finansielle instrumenter som til enhver tid finnes hensiktsmessig, herunder aksjer i selskapet selv, og for øvrig utøve slik virksomhet som står i naturlig forbindelse med forannevnte.”.

Key figures · 2024

Operating profit
NOK −81,000
Equity
NOK 7.1m
Est. value
NOK 8.3m

Financial health · 2024

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

Who owns EXPLORE CAPITAL II AS?

EXPLORE EQUITY AS
EXPLORE CAPITAL II AS
· NOK −81,000 profit

EXPLORE CAPITAL II AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about EXPLORE CAPITAL II AS

Who owns EXPLORE CAPITAL II AS?

EXPLORE EQUITY AS is the largest registered owner, with 50.0%.

Where is EXPLORE CAPITAL II AS based?

EXPLORE CAPITAL II 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.