BIZTRAC BETA
Dental practice care activities

TANNLEGE JON OLAV AABAKKEN AS

Org. no. 989098608 Limited company (AS) Hamar Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 17.9m
Operating profit NOK 4.1m
Equity NOK 208,000
Incorporated 2005
Employees 9
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TANNLEGE JON OLAV AABAKKEN AS is registered as a limited company in Hamar, Innlandet with organisation number 989098608. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2005 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive kjeveortopedisk praksis og almenn tannlegepraksis.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.9m in revenue and NOK 4.1m in operating profit.

Key figures · 2024

Revenue
NOK 17.9m
Operating profit
NOK 4.1m
Equity
NOK 208,000
Est. value
NOK 14.2m

Financial health · 2024

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

Who owns TANNLEGE JON OLAV AABAKKEN AS?

AABA HOLDING AS
TANNLEGE JON OLAV AABAKKEN AS
NOK 17.9m rev. · NOK 4.1m profit

TANNLEGE JON OLAV AABAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE JON OLAV AABAKKEN AS

Who owns TANNLEGE JON OLAV AABAKKEN AS?

AABA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE JON OLAV AABAKKEN AS?

TANNLEGE JON OLAV AABAKKEN AS had revenue of NOK 17.9m in 2024.

Where is TANNLEGE JON OLAV AABAKKEN AS based?

TANNLEGE JON OLAV AABAKKEN AS has its business address in Hamar.

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.