BIZTRAC BETA
Rental and operating of own or leased real estate

M2 HOLDING AS

Org. no. 986390502 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Operating profit NOK −102,000
Equity NOK 60.5m
Incorporated 2003
Share capital NOK 1.7m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−102k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

M2 HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 986390502. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 1.7m, divided into 1700 shares. The company's stated purpose is: “Investering i fast eiendom, eiendomsdrift, handel, finansielle investeringer, konsulentvirksomhet og forretningsførsel. Selskapet kan engasjere seg i andre selskap.”.

Key figures · 2024

Operating profit
NOK −102,000
Equity
NOK 60.5m
Est. value
NOK 118.2m

Financial health · 2024

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

Who owns M2 HOLDING AS?

JOSTEIN MICHAELSEN
M2 HOLDING AS
· NOK −102,000 profit

M2 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M2 HOLDING AS own?

M2 HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about M2 HOLDING AS

Who owns M2 HOLDING AS?

JOSTEIN MICHAELSEN is the largest registered owner, with 100.0%.

Who is the general manager of M2 HOLDING AS?

Jostein Michaelsen is registered as general manager of M2 HOLDING AS.

Where is M2 HOLDING AS based?

M2 HOLDING AS has its business address in Hjellestad.

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.