BIZTRAC BETA
Dental practice care activities

TANNLEGE SIRI LJØKJEL AS

Org. no. 926014919 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 724,000
Operating profit NOK 162,000
Equity NOK 566,000
Incorporated 2020
Share capital NOK 70,000

TANNLEGE SIRI LJØKJEL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926014919. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2020. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Tilby tannlegetjenester, og investere i næringsvirksomhet, herunder fond og aksjer, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 724,000 in revenue and NOK 162,000 in operating profit.

Key figures · 2025

Revenue
NOK 724,000
Operating profit
NOK 162,000
Equity
NOK 566,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns TANNLEGE SIRI LJØKJEL AS?

SIRI LJØKJEL GAUNDAL
TANNLEGE SIRI LJØKJEL AS
NOK 724,000 rev. · NOK 162,000 profit

TANNLEGE SIRI LJØKJEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE SIRI LJØKJEL AS

Who owns TANNLEGE SIRI LJØKJEL AS?

SIRI LJØKJEL GAUNDAL is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE SIRI LJØKJEL AS?

TANNLEGE SIRI LJØKJEL AS had revenue of NOK 724,000 in 2025.

Who is the general manager of TANNLEGE SIRI LJØKJEL AS?

Siri Ljøkjel Gaundal is registered as general manager of TANNLEGE SIRI LJØKJEL AS.

Where is TANNLEGE SIRI LJØKJEL AS based?

TANNLEGE SIRI LJØKJEL 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.