biztrac. BETA
COMPANY REGISTER PROFILE
932737965 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠MM SERVICE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Combined facilities support activities

MM SERVICE AS

Org. no. 932737965 Limited company (AS) Grimstad Incorporated 2023 In liquidation
Revenue 2025 NOK 10,000
Operating profit NOK −13,000
Equity NOK 5,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

MM SERVICE AS is registered as a limited company in Grimstad, Agder with organisation number 932737965. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Vaktmestertjenester, byggetjenester, brøyting, kjøp og salg, med mere.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
▼ −80 %
Operating profit
NOK −13,000
▲ +13 %
Equity
NOK 5,000
▼ −68 %

Financial health · 2025

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

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

Who owns MM SERVICE AS?

MM SERVICE AS
NOK 10,000 rev. · NOK −13,000 profit

MM SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MM SERVICE AS

Who owns MM SERVICE AS?

Thomas Gjerulfsen Christensen is the largest registered owner, with 100.0%.

What is the revenue of MM SERVICE AS?

MM SERVICE AS had revenue of NOK 10,000 in 2025.

Where is MM SERVICE AS based?

MM SERVICE AS has its business address in Grimstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.