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

HAUGESUND TANNMEDISIN AS

Org. no. 922233616 Limited company (AS) Haugesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 3.4m
Equity NOK 2.7m
Incorporated 2019
Employees 5
Share capital NOK 30,000

HAUGESUND TANNMEDISIN AS is registered as a limited company in Haugesund, Rogaland with organisation number 922233616. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 2 shares. The company's stated purpose is: “Drift av tannhelsetjenester og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 3.4m in operating profit.

Former names: PEER REVIEW JOURNAL 1 AS, DENTAL STORE AS

Key figures · 2025

Revenue
NOK 8.9m
▲ +169 %
Operating profit
NOK 3.4m
▲ +296 %
Equity
NOK 2.7m
▲ +293 %
Est. value
NOK 8.5m

Financial health · 2025

Liquidity
3.17
Very good
Current assets ÷ current liabilities
Profitability
76.2%
Very good
Return on total assets
Solidity
46.4%
Very good
Equity as a share of total capital

Who owns HAUGESUND TANNMEDISIN AS?

HAUGESUND TANNMEDISIN AS
NOK 8.9m rev. · NOK 3.4m profit

HAUGESUND TANNMEDISIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAUGESUND TANNMEDISIN AS

Who owns HAUGESUND TANNMEDISIN AS?

TANNLEGE ERIK K. MAULAND AS is the largest registered owner, with 100.0%.

What is the revenue of HAUGESUND TANNMEDISIN AS?

HAUGESUND TANNMEDISIN AS had revenue of NOK 8.9m in 2025.

Where is HAUGESUND TANNMEDISIN AS based?

HAUGESUND TANNMEDISIN 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 03.10.2026.

Report a problem

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