BIZTRAC BETA
Restaurant activities

NISHIKI SUSHI & WOK AS

Org. no. 930123951 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK −48,000
Equity NOK 930,000
Incorporated 2022
Employees 10
Share capital NOK 30,000

Signals

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

NISHIKI SUSHI & WOK AS is registered as a limited company in Oslo, Oslo with organisation number 930123951. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Restaurantvirksomhet og annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK −48,000
Equity
NOK 930,000
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns NISHIKI SUSHI & WOK AS?

THI MY HIEN TRAN
NISHIKI SUSHI & WOK AS
NOK 7.4m rev. · NOK −48,000 profit

NISHIKI SUSHI & WOK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NISHIKI SUSHI & WOK AS

Who owns NISHIKI SUSHI & WOK AS?

THI MY HIEN TRAN is the largest registered owner, with 100.0%.

What is the revenue of NISHIKI SUSHI & WOK AS?

NISHIKI SUSHI & WOK AS had revenue of NOK 7.4m in 2024.

Who is the general manager of NISHIKI SUSHI & WOK AS?

Thi My Hien Tran is registered as general manager of NISHIKI SUSHI & WOK AS.

Where is NISHIKI SUSHI & WOK AS based?

NISHIKI SUSHI & WOK 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.