BIZTRAC BETA
Dental practice care activities

ANNE KJÆRENG AS

Org. no. 984802560 Limited company (AS) Tromsø Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 922,000
Equity NOK 1.6m
Incorporated 2002
Employees 6
Share capital NOK 100,000

ANNE KJÆRENG AS is registered as a limited company in Tromsø, Troms with organisation number 984802560. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2002 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og konsulentarbeid i tilknytning til dette. Videre investering i annen næringsvirksomhet og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 922,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 922,000
Equity
NOK 1.6m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns ANNE KJÆRENG AS?

ANNE KJÆRENG
ANNE KJÆRENG AS
NOK 5.0m rev. · NOK 922,000 profit

ANNE KJÆRENG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ANNE KJÆRENG AS own?

ANNE KJÆRENG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ANNE KJÆRENG AS

Who owns ANNE KJÆRENG AS?

ANNE KJÆRENG is the largest registered owner, with 100.0%.

What is the revenue of ANNE KJÆRENG AS?

ANNE KJÆRENG AS had revenue of NOK 5.0m in 2025.

Who is the general manager of ANNE KJÆRENG AS?

Anne Kjæreng is registered as general manager of ANNE KJÆRENG AS.

Where is ANNE KJÆRENG AS based?

ANNE KJÆRENG AS has its business address in Tromsø.

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.