BIZTRAC BETA
Retail sale of pharmaceutical products

APOTEKET I SON AS

Org. no. 991728147 Limited company (AS) Vestby Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 43.6m
Operating profit NOK 1.5m
Equity NOK 110,000
Incorporated 2007
Employees 25
Share capital NOK 100,000

APOTEKET I SON AS is registered as a limited company in Vestby, Akershus with organisation number 991728147. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2007 and has 25 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av legemidler og helserelaterte produkter samt naturlig tilhørende handelsvarer, fortrinnsvis ved apotekdrift, samt hva hermed står i forbindelse herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 43.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 43.6m
Operating profit
NOK 1.5m
Equity
NOK 110,000
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns APOTEKET I SON AS?

VALLE TANGEN AS
APOTEKET I SON AS
NOK 43.6m rev. · NOK 1.5m profit

APOTEKET I SON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about APOTEKET I SON AS

Who owns APOTEKET I SON AS?

VALLE TANGEN AS is the largest registered owner, with 50.0%.

What is the revenue of APOTEKET I SON AS?

APOTEKET I SON AS had revenue of NOK 43.6m in 2024.

Who is the general manager of APOTEKET I SON AS?

Inge Valle Tangen is registered as general manager of APOTEKET I SON AS.

Where is APOTEKET I SON AS based?

APOTEKET I SON AS has its business address in Son.

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.