BIZTRAC BETA
Other captive investment companies

MAP HOLDCO AS

Org. no. 918594302 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −110,000
Equity NOK 333,000
Incorporated 2017
Share capital NOK 90,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−110k kr).

MAP HOLDCO AS is registered as a limited company in Oslo, Oslo with organisation number 918594302. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 90,000, divided into 30000 shares. The company's stated purpose is: “Investere i skips og offshore relatert virksomhet, herunder egenkapital og gjeldsfinansierte plattformer som skal finansiere denne typen forretninger og annen relatert virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −110,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −110,000
Equity
NOK 333,000
Est. value
NOK 74.8m

Financial health · 2024

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

Who owns MAP HOLDCO AS?

SONGA INVESTMENTS AS
MAP HOLDCO AS
NOK 0 rev. · NOK −110,000 profit

MAP HOLDCO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MAP HOLDCO AS own?

MAP HOLDCO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MAP HOLDCO AS

Who owns MAP HOLDCO AS?

SONGA INVESTMENTS AS is the largest registered owner, with 37.3%.

What is the revenue of MAP HOLDCO AS?

MAP HOLDCO AS had revenue of NOK 0 in 2024.

Where is MAP HOLDCO AS based?

MAP HOLDCO 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.