BIZTRAC BETA
Restaurant activities

CYCLO SPISEBAR AS

Org. no. 998284058 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK −50,000
Equity NOK −103,000
Incorporated 2012
Employees 9
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−103k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−50k kr).

CYCLO SPISEBAR AS is registered as a limited company in Bergen, Vestland with organisation number 998284058. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kafe- og restaurantdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK −50,000
Equity
NOK −103,000

Financial health · 2024

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

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

Who owns CYCLO SPISEBAR AS?

JESSICA VAN TRAN
CYCLO SPISEBAR AS
NOK 7.4m rev. · NOK −50,000 profit

CYCLO SPISEBAR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CYCLO SPISEBAR AS

Who owns CYCLO SPISEBAR AS?

JESSICA VAN TRAN is the largest registered owner, with 50.0%.

What is the revenue of CYCLO SPISEBAR AS?

CYCLO SPISEBAR AS had revenue of NOK 7.4m in 2024.

Who is the general manager of CYCLO SPISEBAR AS?

Thanh Phong Vo is registered as general manager of CYCLO SPISEBAR AS.

Where is CYCLO SPISEBAR AS based?

CYCLO SPISEBAR 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.