biztrac. BETA
COMPANY REGISTER PROFILE
997069269 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Dental practice care activities

TILLER TANNHELSE DA

Org. no. 997069269 General partnership with shared liability (DA) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 946
Equity NOK 5
Incorporated 2011

TILLER TANNHELSE DA is registered as a general partnership with shared liability in Trondheim, Trøndelag with organisation number 997069269. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2011. The company's stated purpose is: “Generell tannlegevirksomhet, kjøp/salg, import, investeringer i fast eiendom, deltagelse i andre virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 946 in operating profit.

Former names: TANNLEGENE KLØVE OG STERNER DA

Key figures · 2025

Revenue
NOK 2.9m
▼ −5 %
Operating profit
NOK 946
▼ −68 %
Equity
NOK 5
▲ +0 %
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns TILLER TANNHELSE DA?

No shareholders are registered for TILLER TANNHELSE DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TILLER TANNHELSE DA

What is the revenue of TILLER TANNHELSE DA?

TILLER TANNHELSE DA had revenue of NOK 2.9m in 2025.

Who is the general manager of TILLER TANNHELSE DA?

Steinar Stevik Kløve is registered as general manager of TILLER TANNHELSE DA.

Where is TILLER TANNHELSE DA based?

TILLER TANNHELSE DA has its business address in Tiller.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.