BIZTRAC BETA
Restaurant activities

BEIJING CUISINE AS

Org. no. 917406952 Limited company (AS) Sandnes Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −42,000
Equity NOK −477,000
Incorporated 2016
Share capital NOK 50,000

Signals

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

BEIJING CUISINE AS is registered as a limited company in Sandnes, Rogaland with organisation number 917406952. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Restaurantvirksomhet og import av varer, samt alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −42,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −42,000
Equity
NOK −477,000

Financial health · 2025

Liquidity
3.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-229.1%
Weak
Equity as a share of total capital

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

Who owns BEIJING CUISINE AS?

WEI XIONG FENG
BEIJING CUISINE AS
NOK 0 rev. · NOK −42,000 profit

BEIJING CUISINE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEIJING CUISINE AS

Who owns BEIJING CUISINE AS?

WEI XIONG FENG is the largest registered owner, with 100.0%.

What is the revenue of BEIJING CUISINE AS?

BEIJING CUISINE AS had revenue of NOK 0 in 2024.

Where is BEIJING CUISINE AS based?

BEIJING CUISINE AS has its business address in Sandnes.

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.