BIZTRAC BETA
COMPANY REGISTER PROFILE
992153040 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of pharmaceutical products

APOTEK SPITSBERGEN AS

Org. no. 992153040 Limited company (AS) Svalbard Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 13.5m
Operating profit NOK 1.3m
Equity NOK 5.9m
Incorporated 2008
Share capital NOK 100,000

APOTEK SPITSBERGEN AS is registered as a limited company in Svalbard, Svalbard with organisation number 992153040. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av apotekvarer, andre helseprodukter og farmasøytiske tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 13.5m
▲ +7 %
Operating profit
NOK 1.3m
▼ −23 %
Equity
NOK 5.9m
▲ +13 %
Est. value
NOK 8.3m

Financial health · 2025

Liquidity
2.61
Very good
Current assets ÷ current liabilities
Profitability
17.8%
Very good
Return on total assets
Solidity
76.6%
Very good
Equity as a share of total capital

Who owns APOTEK SPITSBERGEN AS?

APOTEK SPITSBERGEN AS
NOK 13.5m rev. · NOK 1.3m profit

APOTEK SPITSBERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about APOTEK SPITSBERGEN AS

Who owns APOTEK SPITSBERGEN AS?

BERIT FOSSLAND is the largest registered owner, with 100.0%.

What is the revenue of APOTEK SPITSBERGEN AS?

APOTEK SPITSBERGEN AS had revenue of NOK 13.5m in 2025.

Who is the general manager of APOTEK SPITSBERGEN AS?

Borghild Yttredal is registered as general manager of APOTEK SPITSBERGEN AS.

Where is APOTEK SPITSBERGEN AS based?

APOTEK SPITSBERGEN AS has its business address in Longyearbyen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.