biztrac. BETA
COMPANY REGISTER PROFILE
885186912 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

SZE CHUAN HOUSE AS

Org. no. 885186912 Limited company (AS) Bergen Incorporated 2002 Active
Revenue 2025 NOK 7.9m
Operating profit NOK 342,000
Equity NOK 842,000
Incorporated 2002
Employees 10
Share capital NOK 300,000

SZE CHUAN HOUSE AS is registered as a limited company in Bergen, Vestland with organisation number 885186912. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2002 and has 10 registered employees. Registered share capital is NOK 300,000, divided into 150 shares. The company's stated purpose is: “Kafe og restaurantvirksomhet, herunder servering av varm og kald mat og alkoholholdige drikker og hva som herved naturlig er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 342,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.9m
▲ +9 %
Operating profit
NOK 342,000
▼ −52 %
Equity
NOK 842,000
▲ +3 %
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
14.5%
Good
Return on total assets
Solidity
30.2%
Good
Equity as a share of total capital

Who owns SZE CHUAN HOUSE AS?

SZE CHUAN HOUSE AS
NOK 7.9m rev. · NOK 342,000 profit

SZE CHUAN HOUSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SZE CHUAN HOUSE AS

Who owns SZE CHUAN HOUSE AS?

Weicheng Zhang is the largest registered owner, with 100.0%.

What is the revenue of SZE CHUAN HOUSE AS?

SZE CHUAN HOUSE AS had revenue of NOK 7.9m in 2025.

Who is the general manager of SZE CHUAN HOUSE AS?

Xue Lan Liang is registered as general manager of SZE CHUAN HOUSE AS.

Where is SZE CHUAN HOUSE AS based?

SZE CHUAN HOUSE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.