BIZTRAC BETA
Retail sale of pharmaceutical products

DITT APOTEK BERGEN BRYGGE AS

Org. no. 920445403 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 20.2m
Operating profit NOK 1.7m
Equity NOK 275,000
Incorporated 2018
Employees 9
Share capital NOK 600,000

Signals

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

DITT APOTEK BERGEN BRYGGE AS is registered as a limited company in Bergen, Vestland with organisation number 920445403. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 600,000, divided into 1000 shares. The company's stated purpose is: “Butikkhandel med apotekvarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 20.2m
Operating profit
NOK 1.7m
Equity
NOK 275,000
Est. value
NOK 5.1m

Financial health · 2024

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

Who owns DITT APOTEK BERGEN BRYGGE AS?

NANSEN OUTDOOR STORE BERGEN AS
DITT APOTEK BERGEN BRYGGE AS
NOK 20.2m rev. · NOK 1.7m profit

DITT APOTEK BERGEN BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DITT APOTEK BERGEN BRYGGE AS

Who owns DITT APOTEK BERGEN BRYGGE AS?

NANSEN OUTDOOR STORE BERGEN AS is the largest registered owner, with 100.0%.

What is the revenue of DITT APOTEK BERGEN BRYGGE AS?

DITT APOTEK BERGEN BRYGGE AS had revenue of NOK 20.2m in 2024.

Where is DITT APOTEK BERGEN BRYGGE AS based?

DITT APOTEK BERGEN BRYGGE AS has its business address in Bergen.

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.