BIZTRAC BETA
Dental practice care activities

LUSTER TANNKLINIKK AS

Org. no. 918006095 Limited company (AS) Luster Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 757,000
Equity NOK −1.2m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).

LUSTER TANNKLINIKK AS is registered as a limited company in Luster, Vestland with organisation number 918006095. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tannhelsetenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 757,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 757,000
Equity
NOK −1.2m
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
2.51
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-26.0%
Weak
Equity as a share of total capital

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

Who owns LUSTER TANNKLINIKK AS?

LARS OLAV HALLERÅKER
LUSTER TANNKLINIKK AS
NOK 6.2m rev. · NOK 757,000 profit

LUSTER TANNKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUSTER TANNKLINIKK AS

Who owns LUSTER TANNKLINIKK AS?

LARS OLAV HALLERÅKER is the largest registered owner, with 50.0%.

What is the revenue of LUSTER TANNKLINIKK AS?

LUSTER TANNKLINIKK AS had revenue of NOK 6.2m in 2025.

Who is the general manager of LUSTER TANNKLINIKK AS?

Anne Lene Sygna Halleråker is registered as general manager of LUSTER TANNKLINIKK AS.

Where is LUSTER TANNKLINIKK AS based?

LUSTER TANNKLINIKK AS has its business address in Gaupne.

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.