BIZTRAC BETA
Uoppgitt

METESA HOLDING AS

Org. no. 934306325 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −641,000
Equity NOK 171.9m
Incorporated 2024
Share capital NOK 12.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−641k kr).
  • Nylig endring 2026-02-16 Adresseendring registrert 2026-02-16.

METESA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 934306325. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 12.0m, divided into 23923983 shares. The company's stated purpose is: “Å investere direkte eller indirekte i selskaper relatert til helsesektoren eller livsvitenskap, 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 · 2024

Operating profit
NOK −641,000
Equity
NOK 171.9m
Est. value
NOK 202.0m

Financial health · 2024

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

Who owns METESA HOLDING AS?

SP TOPCO I AS
METESA HOLDING AS
· NOK −641,000 profit

METESA HOLDING AS has 14 registered shareholders:

All shareholders and roles →

Which companies does METESA HOLDING AS own?

METESA HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about METESA HOLDING AS

Who owns METESA HOLDING AS?

SP TOPCO I AS is the largest registered owner, with 48.5%.

Where is METESA HOLDING AS based?

METESA HOLDING 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.