BIZTRAC BETA
COMPANY REGISTER PROFILE
932739550 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

XUANLONG AS

Org. no. 932739550 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK −271,000
Equity NOK −219,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

XUANLONG AS is registered as a limited company in Oslo, Oslo with organisation number 932739550. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Sushi og asiatisk varmmat take away restaurant drift.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK −271,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK −271,000
Equity
NOK −219,000

Financial health · 2025

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

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

Who owns XUANLONG AS?

LONG VAN TRAN
XUANLONG AS
NOK 5.8m rev. · NOK −271,000 profit

XUANLONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about XUANLONG AS

Who owns XUANLONG AS?

LONG VAN TRAN is the largest registered owner, with 50.0%.

What is the revenue of XUANLONG AS?

XUANLONG AS had revenue of NOK 5.8m in 2025.

Who is the general manager of XUANLONG AS?

Long Van Tran is registered as general manager of XUANLONG AS.

Where is XUANLONG AS based?

XUANLONG 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.