BIZTRAC BETA
Uoppgitt

SP TOPCO 4 AS

Org. no. 829285452 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 15,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-16 Adresseendring registrert 2026-02-16.

SP TOPCO 4 AS is registered as a limited company in Oslo, Oslo with organisation number 829285452. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere direkte eller indirekte i selskaper relatert til helsesektoren, herunder gjennom deltagelse i hel- eller deleide selskaper eller andre sammenslutninger eller investere i andre finansielle instrumenter som direkte eller indirekte kan være egnet til å gi selskapet tilgang til investeringer relatert til helsesektoren, samt alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 15,000
Est. value
NOK 18,000

Financial health · 2025

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

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

Who owns SP TOPCO 4 AS?

SERENDIPITY PARTNERS FUND AS
SP TOPCO 4 AS
· NOK −5,000 profit

SP TOPCO 4 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SP TOPCO 4 AS

Who owns SP TOPCO 4 AS?

SERENDIPITY PARTNERS FUND AS is the largest registered owner, with 99.0%.

Where is SP TOPCO 4 AS based?

SP TOPCO 4 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.