BIZTRAC BETA
Dental practice care activities

STANGE DENTAL AS

Org. no. 931723731 Limited company (AS) Stange Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −154,000
Equity NOK 877,000
Incorporated 2023
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−154k kr).

STANGE DENTAL AS is registered as a limited company in Stange, Innlandet with organisation number 931723731. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2023. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Tannhelsetjenester og annet som naturlig faller under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −154,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −154,000
Equity
NOK 877,000
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
5.66
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.5%
Good
Equity as a share of total capital

Who owns STANGE DENTAL AS?

ANOVIA AS
STANGE DENTAL AS
NOK 3.0m rev. · NOK −154,000 profit

STANGE DENTAL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STANGE DENTAL AS own?

STANGE DENTAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STANGE DENTAL AS

Who owns STANGE DENTAL AS?

ANOVIA AS is the largest registered owner, with 50.0%.

What is the revenue of STANGE DENTAL AS?

STANGE DENTAL AS had revenue of NOK 3.0m in 2024.

Who is the general manager of STANGE DENTAL AS?

Ricky Dapinder Singh Gill is registered as general manager of STANGE DENTAL AS.

Where is STANGE DENTAL AS based?

STANGE DENTAL AS has its business address in Stange.

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.