BIZTRAC BETA
Retail sale of pharmaceutical products

HUNNDALEN APOTEK AS

Org. no. 933672425 Limited company (AS) Gjøvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −240,000
Equity NOK 516,000
Incorporated 2024
Employees 7
Share capital NOK 800,000

Signals

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

HUNNDALEN APOTEK AS is registered as a limited company in Gjøvik, Innlandet with organisation number 933672425. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 800,000, divided into 800 shares. The company's stated purpose is: “Eie og drive apotek og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −240,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK −240,000
Equity
NOK 516,000
Est. value
NOK 645,000

Financial health · 2024

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

Who owns HUNNDALEN APOTEK AS?

NATASA GLIGORIC
HUNNDALEN APOTEK AS
NOK 3.2m rev. · NOK −240,000 profit

HUNNDALEN APOTEK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HUNNDALEN APOTEK AS

Who owns HUNNDALEN APOTEK AS?

NATASA GLIGORIC is the largest registered owner, with 25.0%.

What is the revenue of HUNNDALEN APOTEK AS?

HUNNDALEN APOTEK AS had revenue of NOK 3.2m in 2025.

Who is the general manager of HUNNDALEN APOTEK AS?

Natasa Gligoric is registered as general manager of HUNNDALEN APOTEK AS.

Where is HUNNDALEN APOTEK AS based?

HUNNDALEN APOTEK AS has its business address in Hunndalen.

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.