BIZTRAC BETA
Dental practice care activities

TANNLEGENE I DOKTORGÅRDEN AS

Org. no. 998916402 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 341,000
Equity NOK 148,000
Incorporated 2012
Share capital NOK 30,000

TANNLEGENE I DOKTORGÅRDEN AS is registered as a limited company in Asker, Akershus with organisation number 998916402. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tannhelsetjenester og hva dermed står i forbindelse, samt delta i ande selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 341,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 341,000
Equity
NOK 148,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.8%
Satisfactory
Equity as a share of total capital

Who owns TANNLEGENE I DOKTORGÅRDEN AS?

EVA HALBRENDT TØMMERNES
TANNLEGENE I DOKTORGÅRDEN AS
NOK 4.8m rev. · NOK 341,000 profit

TANNLEGENE I DOKTORGÅRDEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANNLEGENE I DOKTORGÅRDEN AS

Who owns TANNLEGENE I DOKTORGÅRDEN AS?

EVA HALBRENDT TØMMERNES is the largest registered owner, with 50.0%.

What is the revenue of TANNLEGENE I DOKTORGÅRDEN AS?

TANNLEGENE I DOKTORGÅRDEN AS had revenue of NOK 4.8m in 2025.

Who is the general manager of TANNLEGENE I DOKTORGÅRDEN AS?

Øystein Ås Løberg is registered as general manager of TANNLEGENE I DOKTORGÅRDEN AS.

Where is TANNLEGENE I DOKTORGÅRDEN AS based?

TANNLEGENE I DOKTORGÅRDEN AS has its business address in Slemmestad.

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.