BIZTRAC BETA
Restaurant activities

JAPO SUSHI FROGNER AS

Org. no. 816607922 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 823,000
Operating profit NOK 396,000
Equity NOK −1.6m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).

JAPO SUSHI FROGNER AS is registered as a limited company in Oslo, Oslo with organisation number 816607922. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Take away og sushi bar.”. The most recent filed accounts, for the 2024 financial year, show NOK 823,000 in revenue and NOK 396,000 in operating profit.

Key figures · 2024

Revenue
NOK 823,000
Operating profit
NOK 396,000
Equity
NOK −1.6m
Est. value
NOK 1.8m

Financial health · 2024

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

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

Who owns JAPO SUSHI FROGNER AS?

JAPO HENRY AS
JAPO SUSHI FROGNER AS
NOK 823,000 rev. · NOK 396,000 profit

JAPO SUSHI FROGNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAPO SUSHI FROGNER AS

Who owns JAPO SUSHI FROGNER AS?

JAPO HENRY AS is the largest registered owner, with 100.0%.

What is the revenue of JAPO SUSHI FROGNER AS?

JAPO SUSHI FROGNER AS had revenue of NOK 823,000 in 2024.

Who is the general manager of JAPO SUSHI FROGNER AS?

Henry Nguyen is registered as general manager of JAPO SUSHI FROGNER AS.

Where is JAPO SUSHI FROGNER AS based?

JAPO SUSHI FROGNER 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.