BIZTRAC BETA
Restaurant activities

JAPANSUSHI AS

Org. no. 921823274 Limited company (AS) Hamar Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK −321,000
Equity NOK −84,000
Incorporated 2018
Employees 10
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−84k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−321k kr).

JAPANSUSHI AS is registered as a limited company in Hamar, Innlandet with organisation number 921823274. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restauranter og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK −321,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK −321,000
Equity
NOK −84,000

Financial health · 2024

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

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

Who owns JAPANSUSHI AS?

HUU PHUC PHAM
JAPANSUSHI AS
NOK 5.8m rev. · NOK −321,000 profit

JAPANSUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAPANSUSHI AS

Who owns JAPANSUSHI AS?

HUU PHUC PHAM is the largest registered owner, with 100.0%.

What is the revenue of JAPANSUSHI AS?

JAPANSUSHI AS had revenue of NOK 5.8m in 2024.

Who is the general manager of JAPANSUSHI AS?

Huu Phuc Pham is registered as general manager of JAPANSUSHI AS.

Where is JAPANSUSHI AS based?

JAPANSUSHI AS has its business address in Hamar.

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.