BIZTRAC BETA
Dental practice care activities

TANNHELSEHUSET BERGEN AS

Org. no. 920416675 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 11.5m
Operating profit NOK 1.5m
Equity NOK 355,000
Incorporated 2018
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TANNHELSEHUSET BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 920416675. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2018 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av tannlegekontor, levering av tannhelsetjenester samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.5m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 11.5m
Operating profit
NOK 1.5m
Equity
NOK 355,000
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns TANNHELSEHUSET BERGEN AS?

UODALRICH HOLDING AS
TANNHELSEHUSET BERGEN AS
NOK 11.5m rev. · NOK 1.5m profit

TANNHELSEHUSET BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNHELSEHUSET BERGEN AS

Who owns TANNHELSEHUSET BERGEN AS?

UODALRICH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TANNHELSEHUSET BERGEN AS?

TANNHELSEHUSET BERGEN AS had revenue of NOK 11.5m in 2024.

Where is TANNHELSEHUSET BERGEN AS based?

TANNHELSEHUSET BERGEN AS has its business address in Laksevåg.

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.