BIZTRAC BETA
Construction of residential and non-residential buildings

MM SERVICE BYGG AS

Org. no. 833903772 Limited company (AS) Giske Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

MM SERVICE BYGG AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 833903772. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rehabilitering av bygg. Snekkerarbeid. Generelle byggearbeider og andre lignende arbeider.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 15,000
Est. value
NOK 16,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MM SERVICE BYGG AS?

MARCIN NIEC
MM SERVICE BYGG AS
NOK 0 rev. · NOK −9,000 profit

MM SERVICE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MM SERVICE BYGG AS

Who owns MM SERVICE BYGG AS?

MARCIN NIEC is the largest registered owner, with 100.0%.

What is the revenue of MM SERVICE BYGG AS?

MM SERVICE BYGG AS had revenue of NOK 0 in 2024.

Who is the general manager of MM SERVICE BYGG AS?

Marcin Niec is registered as general manager of MM SERVICE BYGG AS.

Where is MM SERVICE BYGG AS based?

MM SERVICE BYGG AS has its business address in Valderøya.

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.