BIZTRAC BETA
Restaurant activities

CAI KJØKKEN AS

Org. no. 926398024 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 445,000
Operating profit NOK 147,000
Equity NOK −192,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−192k kr).

CAI KJØKKEN AS is registered as a limited company in Oslo, Oslo with organisation number 926398024. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Restaurant/pub, kulturell aktivitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 445,000 in revenue and NOK 147,000 in operating profit.

Key figures · 2025

Revenue
NOK 445,000
Operating profit
NOK 147,000
Equity
NOK −192,000
Est. value
NOK 668,000

Financial health · 2025

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

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

Who owns CAI KJØKKEN AS?

SHUJUN CAI
CAI KJØKKEN AS
NOK 445,000 rev. · NOK 147,000 profit

CAI KJØKKEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CAI KJØKKEN AS own?

CAI KJØKKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CAI KJØKKEN AS

Who owns CAI KJØKKEN AS?

SHUJUN CAI is the largest registered owner, with 50.0%.

What is the revenue of CAI KJØKKEN AS?

CAI KJØKKEN AS had revenue of NOK 445,000 in 2025.

Who is the general manager of CAI KJØKKEN AS?

Jie Zhang is registered as general manager of CAI KJØKKEN AS.

Where is CAI KJØKKEN AS based?

CAI KJØKKEN AS has its business address in Oslo.

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.