BIZTRAC BETA
Dental practice care activities

TANNLEGENE ASK AS

Org. no. 914569362 Limited company (AS) Kragerø Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 1.4m
Equity NOK 51,000
Incorporated 2014
Employees 6
Share capital NOK 30,000

TANNLEGENE ASK AS is registered as a limited company in Kragerø, Telemark with organisation number 914569362. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tannlegepraksis, herunder nødvendig tilhørende virksomhet, samt investering i verdipapirer, eiendom og andre selskap, samt hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 1.4m
Equity
NOK 51,000
Est. value
NOK 5.7m

Financial health · 2024

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

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

Who owns TANNLEGENE ASK AS?

CATHRINE NORHEIM ASK
TANNLEGENE ASK AS
NOK 8.3m rev. · NOK 1.4m profit

TANNLEGENE ASK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANNLEGENE ASK AS

Who owns TANNLEGENE ASK AS?

CATHRINE NORHEIM ASK is the largest registered owner, with 50.0%.

What is the revenue of TANNLEGENE ASK AS?

TANNLEGENE ASK AS had revenue of NOK 8.3m in 2024.

Who is the general manager of TANNLEGENE ASK AS?

Pål Wolden Ask is registered as general manager of TANNLEGENE ASK AS.

Where is TANNLEGENE ASK AS based?

TANNLEGENE ASK AS has its business address in Kragerø.

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.