BIZTRAC BETA
Dental practice care activities

SANA ORIS TANNKLINIKK AS

Org. no. 819944482 Limited company (AS) Herøy Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 14.8m
Operating profit NOK 856,000
Equity NOK 1.7m
Incorporated 2017
Employees 13
Share capital NOK 2.0m

SANA ORIS TANNKLINIKK AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 819944482. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2017 and has 13 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Tannlegevirksomhet og det som naturlig tilhører dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.8m in revenue and NOK 856,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.8m
Operating profit
NOK 856,000
Equity
NOK 1.7m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.1%
Satisfactory
Equity as a share of total capital

Who owns SANA ORIS TANNKLINIKK AS?

DYRHAUG HOLDING AS
SANA ORIS TANNKLINIKK AS
NOK 14.8m rev. · NOK 856,000 profit

SANA ORIS TANNKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANA ORIS TANNKLINIKK AS

Who owns SANA ORIS TANNKLINIKK AS?

DYRHAUG HOLDING AS is the largest registered owner, with 50.7%.

What is the revenue of SANA ORIS TANNKLINIKK AS?

SANA ORIS TANNKLINIKK AS had revenue of NOK 14.8m in 2024.

Who is the general manager of SANA ORIS TANNKLINIKK AS?

Idunn Berntine Dyrhaug Voldnes is registered as general manager of SANA ORIS TANNKLINIKK AS.

Where is SANA ORIS TANNKLINIKK AS based?

SANA ORIS TANNKLINIKK AS has its business address in Gurskøy.

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.