BIZTRAC BETA
COMPANY REGISTER PROFILE
936905315 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

RECOVER MIPCO AS

Org. no. 936905315 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Equity NOK 967,000
Incorporated 2025
Share capital NOK 489,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-14.

RECOVER MIPCO AS is registered as a limited company in Oslo, Oslo with organisation number 936905315. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 489,000, divided into 4887232 shares. The company's stated purpose is: “Å investere i aksjer og verdipapir samt det som står naturlig i forbindelse med dette.”.

Key figures · 2025

Equity
NOK 967,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns RECOVER MIPCO AS?

RECOVER MIPCO AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does RECOVER MIPCO AS own?

RECOVER MIPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RECOVER MIPCO AS

Who owns RECOVER MIPCO AS?

TED SVEN SEVERIN SOEDERHOLM is the largest registered owner, with 24.8%.

Where is RECOVER MIPCO AS based?

RECOVER MIPCO AS has its business address in Oslo.

Property

Business address c/o Recover AS Lilleakerveien 4A, 0283 Oslo
Cadastral unit 301-9/310/0/0

30 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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