BIZTRAC BETA
Retail sale of pharmaceutical products

LINDESNES APOTEK AS

Org. no. 998692342 Limited company (AS) Lindesnes Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 28.7m
Operating profit NOK 2.4m
Equity NOK 1.2m
Incorporated 2012
Employees 5
Share capital NOK 30,000

LINDESNES APOTEK AS is registered as a limited company in Lindesnes, Agder with organisation number 998692342. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og drive apotek, herunder konsulenttjenester innenfor apotekerbransjen og lege- og helserelaterte produkter, samt øvrig virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.7m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 28.7m
Operating profit
NOK 2.4m
Equity
NOK 1.2m
Est. value
NOK 9.1m

Financial health · 2025

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

Who owns LINDESNES APOTEK AS?

HENRICH DEVINSKY
LINDESNES APOTEK AS
NOK 28.7m rev. · NOK 2.4m profit

LINDESNES APOTEK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LINDESNES APOTEK AS

Who owns LINDESNES APOTEK AS?

HENRICH DEVINSKY is the largest registered owner, with 85.0%.

What is the revenue of LINDESNES APOTEK AS?

LINDESNES APOTEK AS had revenue of NOK 28.7m in 2025.

Who is the general manager of LINDESNES APOTEK AS?

Henrich Devinsky is registered as general manager of LINDESNES APOTEK AS.

Where is LINDESNES APOTEK AS based?

LINDESNES APOTEK AS has its business address in Lindesnes.

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.