BIZTRAC BETA
Restaurant activities

QUE HUONG FOOD AS

Org. no. 925905402 Limited company (AS) Melhus Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 619,000
Operating profit NOK −37,000
Equity NOK 22,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−37k kr).

QUE HUONG FOOD AS is registered as a limited company in Melhus, Trøndelag with organisation number 925905402. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Drift av gatekjøkken, catering og selskapsmat, og alt annet i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 619,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 619,000
Operating profit
NOK −37,000
Equity
NOK 22,000
Est. value
NOK 443,000

Financial health · 2024

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.2%
Weak
Equity as a share of total capital

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

Who owns QUE HUONG FOOD AS?

BJØRN HJALMAR STAURSETH
QUE HUONG FOOD AS
NOK 619,000 rev. · NOK −37,000 profit

QUE HUONG FOOD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about QUE HUONG FOOD AS

Who owns QUE HUONG FOOD AS?

BJØRN HJALMAR STAURSETH is the largest registered owner, with 50.0%.

What is the revenue of QUE HUONG FOOD AS?

QUE HUONG FOOD AS had revenue of NOK 619,000 in 2024.

Who is the general manager of QUE HUONG FOOD AS?

Phuong Thi Tran is registered as general manager of QUE HUONG FOOD AS.

Where is QUE HUONG FOOD AS based?

QUE HUONG FOOD AS has its business address in Lundamo.

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.