BIZTRAC BETA
Wholesale of machine tools

M GROUP HOLDING AS

Org. no. 929450604 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −290,000
Equity NOK 122.6m
Incorporated 2022
Share capital NOK 1.8m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−290k kr).
  • Nylig endring 2026-02-03 Aksjekapital registrert 2026-02-03.

M GROUP HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 929450604. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 2022. Registered share capital is NOK 1.8m, divided into 1804649 shares. The company's stated purpose is: “Eie aksjer eller andeler i andre foretak, og alt som er forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −290,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −290,000
Equity
NOK 122.6m
Est. value
NOK 89.8m

Financial health · 2024

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

Who owns M GROUP HOLDING AS?

AXXELERATOR CAPITAL AS
M GROUP HOLDING AS
NOK 0 rev. · NOK −290,000 profit

M GROUP HOLDING AS has 12 registered shareholders:

All shareholders and roles →

Which companies does M GROUP HOLDING AS own?

M GROUP HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about M GROUP HOLDING AS

Who owns M GROUP HOLDING AS?

AXXELERATOR CAPITAL AS is the largest registered owner, with 72.5%.

What is the revenue of M GROUP HOLDING AS?

M GROUP HOLDING AS had revenue of NOK 0 in 2024.

Where is M GROUP HOLDING AS based?

M GROUP HOLDING AS has its business address in Fornebu.

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.