BIZTRAC BETA
Dental practice care activities

TANNLEGE GUNNAR ODD HAGEN AS

Org. no. 987944986 Limited company (AS) Tinn Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 1.2m
Equity NOK 4.2m
Incorporated 2004
Share capital NOK 500,000

TANNLEGE GUNNAR ODD HAGEN AS is registered as a limited company in Tinn, Telemark with organisation number 987944986. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2004. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Å yte tannlegetjenester og det som står i forbindelse med dette. Selskapet kan også engasjere seg på andre virksomhetsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 1.2m
Equity
NOK 4.2m
Est. value
NOK 7.5m

Financial health · 2024

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

Who owns TANNLEGE GUNNAR ODD HAGEN AS?

GUNNAR ODD HAGEN
TANNLEGE GUNNAR ODD HAGEN AS
NOK 4.3m rev. · NOK 1.2m profit

TANNLEGE GUNNAR ODD HAGEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANNLEGE GUNNAR ODD HAGEN AS

Who owns TANNLEGE GUNNAR ODD HAGEN AS?

GUNNAR ODD HAGEN is the largest registered owner, with 60.0%.

What is the revenue of TANNLEGE GUNNAR ODD HAGEN AS?

TANNLEGE GUNNAR ODD HAGEN AS had revenue of NOK 4.3m in 2024.

Who is the general manager of TANNLEGE GUNNAR ODD HAGEN AS?

Gunnar Odd Hagen is registered as general manager of TANNLEGE GUNNAR ODD HAGEN AS.

Where is TANNLEGE GUNNAR ODD HAGEN AS based?

TANNLEGE GUNNAR ODD HAGEN AS has its business address in Rjukan.

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.