BIZTRAC BETA
Dental practice care activities

TANNHELSEHUSET KILDAHL AS

Org. no. 934064658 Limited company (AS) Bømlo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 13.7m
Operating profit NOK 104,000
Equity NOK 358,000
Incorporated 2024
Employees 9
Share capital NOK 30,000

TANNHELSEHUSET KILDAHL AS is registered as a limited company in Bømlo, Vestland with organisation number 934064658. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2024 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drift av tannhelseklinikk. Videre kan selskapet investere i eiendom og annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.7m in revenue and NOK 104,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.7m
Operating profit
NOK 104,000
Equity
NOK 358,000
Est. value
NOK 699,000

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.7%
Good
Equity as a share of total capital

Who owns TANNHELSEHUSET KILDAHL AS?

KILDAHL HOLDING AS
TANNHELSEHUSET KILDAHL AS
NOK 13.7m rev. · NOK 104,000 profit

TANNHELSEHUSET KILDAHL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNHELSEHUSET KILDAHL AS

Who owns TANNHELSEHUSET KILDAHL AS?

KILDAHL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TANNHELSEHUSET KILDAHL AS?

TANNHELSEHUSET KILDAHL AS had revenue of NOK 13.7m in 2025.

Who is the general manager of TANNHELSEHUSET KILDAHL AS?

Torhild Kildahl is registered as general manager of TANNHELSEHUSET KILDAHL AS.

Where is TANNHELSEHUSET KILDAHL AS based?

TANNHELSEHUSET KILDAHL AS has its business address in Bremnes.

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.