BIZTRAC BETA
Retail sale of pharmaceutical products

LUSTER APOTEK AS

Org. no. 998478383 Limited company (AS) Luster Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 28.0m
Operating profit NOK 249,000
Equity NOK 311,000
Incorporated 2012
Employees 7
Share capital NOK 150,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LUSTER APOTEK AS is registered as a limited company in Luster, Vestland with organisation number 998478383. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Sal av apotekvarer og det som naturleg høyrer til.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.0m in revenue and NOK 249,000 in operating profit.

Key figures · 2024

Revenue
NOK 28.0m
Operating profit
NOK 249,000
Equity
NOK 311,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns LUSTER APOTEK AS?

UTHUS HOLDING AS
LUSTER APOTEK AS
NOK 28.0m rev. · NOK 249,000 profit

LUSTER APOTEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUSTER APOTEK AS

Who owns LUSTER APOTEK AS?

UTHUS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LUSTER APOTEK AS?

LUSTER APOTEK AS had revenue of NOK 28.0m in 2024.

Who is the general manager of LUSTER APOTEK AS?

Stine Eidslott is registered as general manager of LUSTER APOTEK AS.

Where is LUSTER APOTEK AS based?

LUSTER APOTEK AS has its business address in Gaupne.

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.