BIZTRAC BETA
Restaurant activities

DRAGEN FOOD AS

Org. no. 932966956 Limited company (AS) Ringerike Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK −38,000
Equity NOK −258,000
Incorporated 2024
Employees 10
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−258k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).

DRAGEN FOOD AS is registered as a limited company in Ringerike, Buskerud with organisation number 932966956. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Serveringsvirksomhet og annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK −38,000
Equity
NOK −258,000

Financial health · 2025

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

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

Who owns DRAGEN FOOD AS?

QIANG CHENG
DRAGEN FOOD AS
NOK 3.1m rev. · NOK −38,000 profit

DRAGEN FOOD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRAGEN FOOD AS

Who owns DRAGEN FOOD AS?

QIANG CHENG is the largest registered owner, with 100.0%.

What is the revenue of DRAGEN FOOD AS?

DRAGEN FOOD AS had revenue of NOK 3.1m in 2025.

Who is the general manager of DRAGEN FOOD AS?

Qiang Cheng is registered as general manager of DRAGEN FOOD AS.

Where is DRAGEN FOOD AS based?

DRAGEN FOOD AS has its business address in Hønefoss.

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.