BIZTRAC BETA
Dental practice care activities

DRØBAK TANNLEGEVAKT AS

Org. no. 931268902 Limited company (AS) Frogn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 70,000
Equity NOK 542,000
Incorporated 2023
Share capital NOK 30,000

DRØBAK TANNLEGEVAKT AS is registered as a limited company in Frogn, Akershus with organisation number 931268902. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen tannlegearbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 70,000
Equity
NOK 542,000
Est. value
NOK 709,000

Financial health · 2025

Liquidity
-39.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.6%
Very good
Equity as a share of total capital

Who owns DRØBAK TANNLEGEVAKT AS?

ALHOUSAIN AS
DRØBAK TANNLEGEVAKT AS
NOK 3.3m rev. · NOK 70,000 profit

DRØBAK TANNLEGEVAKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRØBAK TANNLEGEVAKT AS

Who owns DRØBAK TANNLEGEVAKT AS?

ALHOUSAIN AS is the largest registered owner, with 100.0%.

What is the revenue of DRØBAK TANNLEGEVAKT AS?

DRØBAK TANNLEGEVAKT AS had revenue of NOK 3.3m in 2025.

Who is the general manager of DRØBAK TANNLEGEVAKT AS?

Mulham Nasser Gboor is registered as general manager of DRØBAK TANNLEGEVAKT AS.

Where is DRØBAK TANNLEGEVAKT AS based?

DRØBAK TANNLEGEVAKT AS has its business address in Drøbak.

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.