BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

BERGEN CANDY AS

Org. no. 933577279 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −130,000
Equity NOK −188,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−188k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−130k kr).

BERGEN CANDY AS is registered as a limited company in Bergen, Vestland with organisation number 933577279. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kioskhandel med bredt vareutvalg med hovedvekt på nærings- og nytelsesmidler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −130,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −130,000
Equity
NOK −188,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BERGEN CANDY AS?

No shareholders are registered for BERGEN CANDY AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BERGEN CANDY AS

What is the revenue of BERGEN CANDY AS?

BERGEN CANDY AS had revenue of NOK 1.8m in 2025.

Who is the general manager of BERGEN CANDY AS?

Leila Sabovic is registered as general manager of BERGEN CANDY AS.

Where is BERGEN CANDY AS based?

BERGEN CANDY 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.