BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

VITALO AS

Org. no. 913298608 Limited company (AS) Frogn Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 4.2m
Equity NOK 8.1m
Incorporated 2014
Share capital NOK 30,000

VITALO AS is registered as a limited company in Frogn, Akershus with organisation number 913298608. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Legevirksomhet med spesialisering innenfor øre, nese, hals. Kjøp og salg av medisinsk utstyr. Omsetning og utleie av fast eiendom, aksjehandel og investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 4.2m
Equity
NOK 8.1m
Est. value
NOK 20.6m

Financial health · 2024

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

Who owns VITALO AS?

KALLE-KUSTAA HEMIÖ
VITALO AS
NOK 8.4m rev. · NOK 4.2m profit

VITALO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VITALO AS own?

VITALO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VITALO AS

Who owns VITALO AS?

KALLE-KUSTAA HEMIÖ is the largest registered owner, with 100.0%.

What is the revenue of VITALO AS?

VITALO AS had revenue of NOK 8.4m in 2024.

Who is the general manager of VITALO AS?

Kalle-Kustaa Hemiö is registered as general manager of VITALO AS.

Where is VITALO AS based?

VITALO 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.