BIZTRAC BETA
Restaurant activities

JAPAN SUSHI AS

Org. no. 921058306 Limited company (AS) Lillehammer Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK 1.6m
Equity NOK 7.0m
Incorporated 2018
Employees 12
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JAPAN SUSHI AS is registered as a limited company in Lillehammer, Innlandet with organisation number 921058306. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 100 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 13.3m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK 1.6m
Equity
NOK 7.0m
Est. value
NOK 10.8m

Financial health · 2024

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

Who owns JAPAN SUSHI AS?

QUAN HOLDING AS
JAPAN SUSHI AS
NOK 13.3m rev. · NOK 1.6m profit

JAPAN SUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAPAN SUSHI AS

Who owns JAPAN SUSHI AS?

QUAN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JAPAN SUSHI AS?

JAPAN SUSHI AS had revenue of NOK 13.3m in 2024.

Who is the general manager of JAPAN SUSHI AS?

Huu Quan Pham is registered as general manager of JAPAN SUSHI AS.

Where is JAPAN SUSHI AS based?

JAPAN SUSHI AS has its business address in Lillehammer.

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.