BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

DINGO MEDICA AS

Org. no. 919480866 Limited company (AS) Hvaler Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 388,000
Equity NOK 517,000
Incorporated 2017
Share capital NOK 30,000

DINGO MEDICA AS is registered as a limited company in Hvaler, Østfold with organisation number 919480866. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Medisinsk konsultasjons virksomhet, helsearbeid innen kirurgi av ortopediske problemstillinger, foredrag innen medisin, og å engasjere seg i beslektede virksomheter, samt alt hva som hermed måtte stå i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 388,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 388,000
Equity
NOK 517,000
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.1%
Good
Equity as a share of total capital

Who owns DINGO MEDICA AS?

DINGO AS
DINGO MEDICA AS
NOK 4.3m rev. · NOK 388,000 profit

DINGO MEDICA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DINGO MEDICA AS

Who owns DINGO MEDICA AS?

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

What is the revenue of DINGO MEDICA AS?

DINGO MEDICA AS had revenue of NOK 4.3m in 2024.

Who is the general manager of DINGO MEDICA AS?

Tom Henry Sundøen is registered as general manager of DINGO MEDICA AS.

Where is DINGO MEDICA AS based?

DINGO MEDICA AS has its business address in Vesterø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.