BIZTRAC BETA
Retail sale of pharmaceutical products

VITUSAPOTEK LANGHUS AS

Org. no. 933820572 Limited company (AS) Nordre Follo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 15.2m
Operating profit NOK −314,000
Equity NOK 155,000
Incorporated 2024
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−314k kr).

VITUSAPOTEK LANGHUS AS is registered as a limited company in Nordre Follo, Akershus with organisation number 933820572. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2024. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Eie og drive apotek og apotekrelaterte aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.2m in revenue and NOK −314,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.2m
Operating profit
NOK −314,000
Equity
NOK 155,000
Est. value
NOK 5.0m

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.6%
Weak
Equity as a share of total capital

Who owns VITUSAPOTEK LANGHUS AS?

PHARMA CARE INVEST AS
VITUSAPOTEK LANGHUS AS
NOK 15.2m rev. · NOK −314,000 profit

VITUSAPOTEK LANGHUS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VITUSAPOTEK LANGHUS AS

Who owns VITUSAPOTEK LANGHUS AS?

PHARMA CARE INVEST AS is the largest registered owner, with 40.0%.

What is the revenue of VITUSAPOTEK LANGHUS AS?

VITUSAPOTEK LANGHUS AS had revenue of NOK 15.2m in 2025.

Who is the general manager of VITUSAPOTEK LANGHUS AS?

Malik Mumtaz Hussain Taqi is registered as general manager of VITUSAPOTEK LANGHUS AS.

Where is VITUSAPOTEK LANGHUS AS based?

VITUSAPOTEK LANGHUS AS has its business address in Langhus.

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.