BIZTRAC BETA
Dental practice care activities

WAAGE TANNLEGESENTER AS

Org. no. 989022539 Limited company (AS) Klepp Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 25.3m
Operating profit NOK 7.8m
Equity NOK 375,000
Incorporated 2005
Employees 12
Share capital NOK 200,000

WAAGE TANNLEGESENTER AS is registered as a limited company in Klepp, Rogaland with organisation number 989022539. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2005 and has 12 registered employees. Registered share capital is NOK 200,000, divided into 6000 shares. The company's stated purpose is: “Tannlegedrift og alt som hermed står i forbindelse heri inkludert deltagelse i andre selskap med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.3m in revenue and NOK 7.8m in operating profit.

Key figures · 2025

Revenue
NOK 25.3m
Operating profit
NOK 7.8m
Equity
NOK 375,000
Est. value
NOK 25.3m

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.6%
Weak
Equity as a share of total capital

Who owns WAAGE TANNLEGESENTER AS?

LARS NORDBØ HOLDING AS
WAAGE TANNLEGESENTER AS
NOK 25.3m rev. · NOK 7.8m profit

WAAGE TANNLEGESENTER AS has 3 registered shareholders:

All shareholders and roles →

Which companies does WAAGE TANNLEGESENTER AS own?

WAAGE TANNLEGESENTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WAAGE TANNLEGESENTER AS

Who owns WAAGE TANNLEGESENTER AS?

LARS NORDBØ HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of WAAGE TANNLEGESENTER AS?

WAAGE TANNLEGESENTER AS had revenue of NOK 25.3m in 2025.

Where is WAAGE TANNLEGESENTER AS based?

WAAGE TANNLEGESENTER AS has its business address in Kleppe.

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.