BIZTRAC BETA
Dental practice care activities

TANNLEGENE I KAFFEHUSET AS

Org. no. 933574431 Limited company (AS) Skien Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 159,000
Equity NOK 98,000
Incorporated 2024
Share capital NOK 200,000

TANNLEGENE I KAFFEHUSET AS is registered as a limited company in Skien, Telemark with organisation number 933574431. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2024. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drift av tannlegekontor, samt annet som naturlig hører innunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 159,000
Equity
NOK 98,000
Est. value
NOK 474,000

Financial health · 2025

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

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

Who owns TANNLEGENE I KAFFEHUSET AS?

HADH HOLDING AS
TANNLEGENE I KAFFEHUSET AS
NOK 5.1m rev. · NOK 159,000 profit

TANNLEGENE I KAFFEHUSET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANNLEGENE I KAFFEHUSET AS

Who owns TANNLEGENE I KAFFEHUSET AS?

HADH HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TANNLEGENE I KAFFEHUSET AS?

TANNLEGENE I KAFFEHUSET AS had revenue of NOK 5.1m in 2025.

Who is the general manager of TANNLEGENE I KAFFEHUSET AS?

Margrethe Kjellsen Westlie is registered as general manager of TANNLEGENE I KAFFEHUSET AS.

Where is TANNLEGENE I KAFFEHUSET AS based?

TANNLEGENE I KAFFEHUSET AS has its business address in Skien.

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.