BIZTRAC BETA
Dental practice care activities

ABELGÅRDEN TANNKLINIKK AS

Org. no. 980399621 Limited company (AS) Trondheim Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 161,000
Equity NOK 735,000
Incorporated 1998
Employees 9
Share capital NOK 30,000

ABELGÅRDEN TANNKLINIKK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 980399621. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 1998 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 50000 shares. The company's stated purpose is: “Tannlegevirksomhet, derunder handel med tannlegeprodukter og alt som står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 161,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 161,000
Equity
NOK 735,000
Est. value
NOK 994,000

Financial health · 2024

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.9%
Satisfactory
Equity as a share of total capital

Who owns ABELGÅRDEN TANNKLINIKK AS?

JAN ROAR RØNNING
ABELGÅRDEN TANNKLINIKK AS
NOK 8.3m rev. · NOK 161,000 profit

ABELGÅRDEN TANNKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ABELGÅRDEN TANNKLINIKK AS

Who owns ABELGÅRDEN TANNKLINIKK AS?

JAN ROAR RØNNING is the largest registered owner, with 50.0%.

What is the revenue of ABELGÅRDEN TANNKLINIKK AS?

ABELGÅRDEN TANNKLINIKK AS had revenue of NOK 8.3m in 2024.

Who is the general manager of ABELGÅRDEN TANNKLINIKK AS?

Tu Kha Truong is registered as general manager of ABELGÅRDEN TANNKLINIKK AS.

Where is ABELGÅRDEN TANNKLINIKK AS based?

ABELGÅRDEN TANNKLINIKK AS has its business address in Trondheim.

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.