BIZTRAC BETA
Restaurant activities

DYNASTIET RESTAURANT AS

Org. no. 989816055 Limited company (AS) Drammen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK 1.6m
Equity NOK 8.2m
Incorporated 2006
Employees 7
Share capital NOK 100,000

DYNASTIET RESTAURANT AS is registered as a limited company in Drammen, Buskerud with organisation number 989816055. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2006 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie samt drifte serveringssted og eiendommer og alt som står i forbindelse med dette - herunder å delta i andre selskaper. Salg av næringsmidler og helsekost.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK 1.6m
Equity
NOK 8.2m
Est. value
NOK 10.8m

Financial health · 2024

Liquidity
7.49
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.8%
Very good
Equity as a share of total capital

Who owns DYNASTIET RESTAURANT AS?

ZHONGFAN XU
DYNASTIET RESTAURANT AS
NOK 8.8m rev. · NOK 1.6m profit

DYNASTIET RESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYNASTIET RESTAURANT AS

Who owns DYNASTIET RESTAURANT AS?

ZHONGFAN XU is the largest registered owner, with 100.0%.

What is the revenue of DYNASTIET RESTAURANT AS?

DYNASTIET RESTAURANT AS had revenue of NOK 8.8m in 2024.

Who is the general manager of DYNASTIET RESTAURANT AS?

Enjing Sun is registered as general manager of DYNASTIET RESTAURANT AS.

Where is DYNASTIET RESTAURANT AS based?

DYNASTIET RESTAURANT AS has its business address in Drammen.

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.