BIZTRAC BETA
Mining of chemical and fertiliser minerals

MAGNESIUM ALLOYS NORWAY AS

Org. no. 921045298 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −22,000
Equity NOK −149,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−149k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).

MAGNESIUM ALLOYS NORWAY AS is registered as a limited company in Oslo, Oslo with organisation number 921045298. The business is classified under mining of chemical and fertiliser minerals (NACE 08.910). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Resirkulering og produksjon av magnesium.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK −149,000

Financial health · 2024

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

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

Who owns MAGNESIUM ALLOYS NORWAY AS?

MAN INDUSTRIAL HOLDINGS LIMITED
MAGNESIUM ALLOYS NORWAY AS
NOK 0 rev. · NOK −22,000 profit

MAGNESIUM ALLOYS NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAGNESIUM ALLOYS NORWAY AS

Who owns MAGNESIUM ALLOYS NORWAY AS?

MAN INDUSTRIAL HOLDINGS LIMITED is the largest registered owner, with 100.0%.

What is the revenue of MAGNESIUM ALLOYS NORWAY AS?

MAGNESIUM ALLOYS NORWAY AS had revenue of NOK 0 in 2024.

Where is MAGNESIUM ALLOYS NORWAY AS based?

MAGNESIUM ALLOYS NORWAY 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.