BIZTRAC BETA
Restaurant activities

852YUMCHA AS

Org. no. 931474375 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 18.4m
Operating profit NOK 1.6m
Equity NOK 2.9m
Incorporated 2023
Employees 27
Share capital NOK 750,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

852YUMCHA AS is registered as a limited company in Oslo, Oslo with organisation number 931474375. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 27 registered employees. Registered share capital is NOK 750,000, divided into 7500 shares. The company's stated purpose is: “Restaurant- og serveringsvirksomhet, handel, og annen virksomhet i forbindelse med dette, herunder deltagelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.4m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 18.4m
Operating profit
NOK 1.6m
Equity
NOK 2.9m
Est. value
NOK 7.1m

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.7%
Good
Equity as a share of total capital

Who owns 852YUMCHA AS?

DINNER-GROUP AS
852YUMCHA AS
NOK 18.4m rev. · NOK 1.6m profit

852YUMCHA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 852YUMCHA AS

Who owns 852YUMCHA AS?

DINNER-GROUP AS is the largest registered owner, with 60.0%.

What is the revenue of 852YUMCHA AS?

852YUMCHA AS had revenue of NOK 18.4m in 2024.

Who is the general manager of 852YUMCHA AS?

Wai Hang Chan is registered as general manager of 852YUMCHA AS.

Where is 852YUMCHA AS based?

852YUMCHA 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.