BIZTRAC BETA
Retail sale of pharmaceutical products

APOVEST AS

Org. no. 994606719 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 123,000
Equity NOK 5.0m
Incorporated 2009
Share capital NOK 2.5m

APOVEST AS is registered as a limited company in Bergen, Vestland with organisation number 994606719. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2009. Registered share capital is NOK 2.5m, divided into 2506 shares. The company's stated purpose is: “Hovedkontortjenester, utleie av fast eiendom, eierskap og drift av apotek, handel med apotekvarer og relaterte produkter, aktuelle konsulent og rådgivningstjenester i eget og underliggende selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 123,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 123,000
Equity
NOK 5.0m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns APOVEST AS?

NORSK MEDISINALDEPOT AS
APOVEST AS
NOK 2.9m rev. · NOK 123,000 profit

APOVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does APOVEST AS own?

APOVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about APOVEST AS

Who owns APOVEST AS?

NORSK MEDISINALDEPOT AS is the largest registered owner, with 49.0%.

What is the revenue of APOVEST AS?

APOVEST AS had revenue of NOK 2.9m in 2024.

Who is the general manager of APOVEST AS?

Håvard Røkke is registered as general manager of APOVEST AS.

Where is APOVEST AS based?

APOVEST AS has its business address in Ulset.

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.