BIZTRAC BETA
Dental practice care activities

MM TANNLEGEKLINIKK AS

Org. no. 917374252 Limited company (AS) Drammen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 1.9m
Equity NOK 3.1m
Incorporated 2016
Share capital NOK 30,000

MM TANNLEGEKLINIKK AS is registered as a limited company in Drammen, Buskerud with organisation number 917374252. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby administrative og faglige tjenester innenfor tannhelsetjenester, og andre sammenlignbare helsetjenester, videre virksomheter med behov for administrative og faglig kompetanse for drift i privat sektor.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 1.9m
Equity
NOK 3.1m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns MM TANNLEGEKLINIKK AS?

MAGDALENA MOLAND
MM TANNLEGEKLINIKK AS
NOK 3.0m rev. · NOK 1.9m profit

MM TANNLEGEKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MM TANNLEGEKLINIKK AS

Who owns MM TANNLEGEKLINIKK AS?

MAGDALENA MOLAND is the largest registered owner, with 100.0%.

What is the revenue of MM TANNLEGEKLINIKK AS?

MM TANNLEGEKLINIKK AS had revenue of NOK 3.0m in 2025.

Who is the general manager of MM TANNLEGEKLINIKK AS?

Magdalena Moland is registered as general manager of MM TANNLEGEKLINIKK AS.

Where is MM TANNLEGEKLINIKK AS based?

MM TANNLEGEKLINIKK AS has its business address in Drammen.

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.