BIZTRAC BETA
Dental practice care activities

TANNLEGE KRISTIN THORUD AS

Org. no. 920296203 Limited company (AS) Lillehammer Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 357,000
Equity NOK 1.6m
Incorporated 2018
Share capital NOK 30,000

TANNLEGE KRISTIN THORUD AS is registered as a limited company in Lillehammer, Innlandet with organisation number 920296203. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og alt som står i forbindelse med dette. Investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 357,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 357,000
Equity
NOK 1.6m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns TANNLEGE KRISTIN THORUD AS?

KRISTIN LILLEMO-THORUD
TANNLEGE KRISTIN THORUD AS
NOK 1.7m rev. · NOK 357,000 profit

TANNLEGE KRISTIN THORUD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TANNLEGE KRISTIN THORUD AS own?

TANNLEGE KRISTIN THORUD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TANNLEGE KRISTIN THORUD AS

Who owns TANNLEGE KRISTIN THORUD AS?

KRISTIN LILLEMO-THORUD is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE KRISTIN THORUD AS?

TANNLEGE KRISTIN THORUD AS had revenue of NOK 1.7m in 2024.

Where is TANNLEGE KRISTIN THORUD AS based?

TANNLEGE KRISTIN THORUD AS has its business address in Lillehammer.

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.