BIZTRAC BETA
Development of building projects

M3 BOLIGER AS

Org. no. 917135177 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 117.8m
Operating profit NOK 14.7m
Equity NOK 3.8m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

M3 BOLIGER AS is registered as a limited company in Oslo, Oslo with organisation number 917135177. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utleie av boliger og dertil tilhørende.”. The most recent filed accounts, for the 2024 financial year, show NOK 117.8m in revenue and NOK 14.7m in operating profit.

Key figures · 2024

Revenue
NOK 117.8m
Operating profit
NOK 14.7m
Equity
NOK 3.8m
Est. value
NOK 30.7m

Financial health · 2024

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

Who owns M3 BOLIGER AS?

M3 BOLIGER INVEST AS
M3 BOLIGER AS
NOK 117.8m rev. · NOK 14.7m profit

M3 BOLIGER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M3 BOLIGER AS own?

M3 BOLIGER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about M3 BOLIGER AS

Who owns M3 BOLIGER AS?

M3 BOLIGER INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of M3 BOLIGER AS?

M3 BOLIGER AS had revenue of NOK 117.8m in 2024.

Who is the general manager of M3 BOLIGER AS?

Marius Bjelland is registered as general manager of M3 BOLIGER AS.

Where is M3 BOLIGER AS based?

M3 BOLIGER 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.