BIZTRAC BETA
Restaurant activities

HUONG NGUYEN HOLDING AS

Org. no. 996814378 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −331
Equity NOK 2.0m
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−331 kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HUONG NGUYEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 996814378. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper og verdipapirer, investering i eiendom og utleie av fast eiendom, samt annet som relaterer seg til dette.”.

Key figures · 2024

Operating profit
NOK −331
Equity
NOK 2.0m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns HUONG NGUYEN HOLDING AS?

XUAN THANH NGUYEN
HUONG NGUYEN HOLDING AS
· NOK −331 profit

HUONG NGUYEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HUONG NGUYEN HOLDING AS own?

HUONG NGUYEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HUONG NGUYEN HOLDING AS

Who owns HUONG NGUYEN HOLDING AS?

XUAN THANH NGUYEN is the largest registered owner, with 50.0%.

Who is the general manager of HUONG NGUYEN HOLDING AS?

Thu Huong Thi Nguyen is registered as general manager of HUONG NGUYEN HOLDING AS.

Where is HUONG NGUYEN HOLDING AS based?

HUONG NGUYEN HOLDING 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.