BIZTRAC BETA
Dental practice care activities

TANNHELSEHUSET HAUGESUND PRODUKTER AS

Org. no. 932993759 Limited company (AS) Haugesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 334,000
Operating profit NOK 103,000
Equity NOK 166,000
Incorporated 2024
Share capital NOK 30,000

TANNHELSEHUSET HAUGESUND PRODUKTER AS is registered as a limited company in Haugesund, Rogaland with organisation number 932993759. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive tannlegevirksomhet, detaljhandel og virksomhet som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 334,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2025

Revenue
NOK 334,000
Operating profit
NOK 103,000
Equity
NOK 166,000
Est. value
NOK 470,000

Financial health · 2025

Liquidity
3.02
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
66.8%
Very good
Equity as a share of total capital

Who owns TANNHELSEHUSET HAUGESUND PRODUKTER AS?

TANNHELSEHUSET HAUGESUND AS
TANNHELSEHUSET HAUGESUND PRODUKTER AS
NOK 334,000 rev. · NOK 103,000 profit

TANNHELSEHUSET HAUGESUND PRODUKTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNHELSEHUSET HAUGESUND PRODUKTER AS

Who owns TANNHELSEHUSET HAUGESUND PRODUKTER AS?

TANNHELSEHUSET HAUGESUND AS is the largest registered owner, with 100.0%.

What is the revenue of TANNHELSEHUSET HAUGESUND PRODUKTER AS?

TANNHELSEHUSET HAUGESUND PRODUKTER AS had revenue of NOK 334,000 in 2025.

Where is TANNHELSEHUSET HAUGESUND PRODUKTER AS based?

TANNHELSEHUSET HAUGESUND PRODUKTER AS has its business address in Haugesund.

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.