BIZTRAC BETA
Construction of residential and non-residential buildings

MM BYGGSERVICE AS

Org. no. 924570385 Limited company (AS) Vestby Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −39,000
Equity NOK 340,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−39k kr).
  • Nylig endring 2026-06-08 Adresseendring registrert 2026-06-08.

MM BYGGSERVICE AS is registered as a limited company in Vestby, Akershus with organisation number 924570385. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bygg, renovering.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −39,000
Equity
NOK 340,000
Est. value
NOK 792,000

Financial health · 2025

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

Who owns MM BYGGSERVICE AS?

MATEUSZ CHLEBOWSKI
MM BYGGSERVICE AS
NOK 1.9m rev. · NOK −39,000 profit

MM BYGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MM BYGGSERVICE AS

Who owns MM BYGGSERVICE AS?

MATEUSZ CHLEBOWSKI is the largest registered owner, with 100.0%.

What is the revenue of MM BYGGSERVICE AS?

MM BYGGSERVICE AS had revenue of NOK 1.9m in 2025.

Who is the general manager of MM BYGGSERVICE AS?

Mateusz Chlebowski is registered as general manager of MM BYGGSERVICE AS.

Where is MM BYGGSERVICE AS based?

MM BYGGSERVICE AS has its business address in Vestby.

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.