BIZTRAC BETA
Dental practice care activities

TANNLEGE CHRISTINE JARLING AS

Org. no. 913885848 Limited company (AS) Harstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 308,000
Equity NOK 927,000
Incorporated 2014
Share capital NOK 30,000

TANNLEGE CHRISTINE JARLING AS is registered as a limited company in Harstad, Troms with organisation number 913885848. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tannhelsetjenester og annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 308,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 308,000
Equity
NOK 927,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns TANNLEGE CHRISTINE JARLING AS?

CHRISTINE JARLING
TANNLEGE CHRISTINE JARLING AS
NOK 1.9m rev. · NOK 308,000 profit

TANNLEGE CHRISTINE JARLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE CHRISTINE JARLING AS

Who owns TANNLEGE CHRISTINE JARLING AS?

CHRISTINE JARLING is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE CHRISTINE JARLING AS?

TANNLEGE CHRISTINE JARLING AS had revenue of NOK 1.9m in 2025.

Who is the general manager of TANNLEGE CHRISTINE JARLING AS?

Christine Jarling is registered as general manager of TANNLEGE CHRISTINE JARLING AS.

Where is TANNLEGE CHRISTINE JARLING AS based?

TANNLEGE CHRISTINE JARLING AS has its business address in Harstad.

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.