BIZTRAC BETA
Rental and operating of own or leased real estate

M2 INVESTERING AS

Org. no. 990660239 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 3.4m
Equity NOK 9.3m
Incorporated 2006
Share capital NOK 1.2m

M2 INVESTERING AS is registered as a limited company in Stavanger, Rogaland with organisation number 990660239. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.2m, divided into 1234600 shares. The company's stated purpose is: “Å drive investeringer og forvaltning av eiendommer og aksjer herunder opprettelse av datterselskaper. I tillegg annet som kan forbindes med dette. Dessuten deltakelse i andre foretak. ”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 3.4m
Equity
NOK 9.3m
Est. value
NOK 12.9m

Financial health · 2025

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

Who owns M2 INVESTERING AS?

HØYER INVESTERING AS
M2 INVESTERING AS
NOK 4.2m rev. · NOK 3.4m profit

M2 INVESTERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about M2 INVESTERING AS

Who owns M2 INVESTERING AS?

HØYER INVESTERING AS is the largest registered owner, with 50.0%.

What is the revenue of M2 INVESTERING AS?

M2 INVESTERING AS had revenue of NOK 4.2m in 2025.

Who is the general manager of M2 INVESTERING AS?

Karl Bjarte Hatteland is registered as general manager of M2 INVESTERING AS.

Where is M2 INVESTERING AS based?

M2 INVESTERING AS has its business address in Hafrsfjord.

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.