BIZTRAC BETA
COMPANY REGISTER PROFILE
988884405 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

MALMAG CAPITAL AS

Org. no. 988884405 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −62,000
Equity NOK 92.6m
Incorporated 2005
Share capital NOK 222,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).

MALMAG CAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 988884405. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 222,000, divided into 111112 shares. The company's stated purpose is: “Kapitalforvaltning i form av finans- og realaktiva og hva hermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −62,000 in operating profit.

Former names: OAP INVEST AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −62,000
▲ +66 %
Equity
NOK 92.6m
▲ +29 %
Est. value
NOK 186.4m

Financial health · 2025

Liquidity
4940.99
Very good
Current assets ÷ current liabilities
Profitability
25.4%
Very good
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns MALMAG CAPITAL AS?

MALMAG CAPITAL AS
NOK 0 rev. · NOK −62,000 profit

MALMAG CAPITAL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MALMAG CAPITAL AS own?

MALMAG CAPITAL AS holds stakes in 11 companies:

See the full ownership structure →

Frequently asked questions about MALMAG CAPITAL AS

Who owns MALMAG CAPITAL AS?

MALMAG AS is the largest registered owner, with 90.0%.

What is the revenue of MALMAG CAPITAL AS?

MALMAG CAPITAL AS had revenue of NOK 0 in 2025.

Where is MALMAG CAPITAL AS based?

MALMAG CAPITAL 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 02.09.2026.

Report a problem

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