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

MYMY SUSHI AS

Org. no. 918572694 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 109,000
Equity NOK −24,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−24k kr).

MYMY SUSHI AS is registered as a limited company in Oslo, Oslo with organisation number 918572694. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017. 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 1.9m in revenue and NOK 109,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 109,000
Equity
NOK −24,000
Est. value
NOK 641,000

Financial health · 2024

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

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

Who owns MYMY SUSHI AS?

NUONG MY THI TRUONG
MYMY SUSHI AS
NOK 1.9m rev. · NOK 109,000 profit

MYMY SUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYMY SUSHI AS

Who owns MYMY SUSHI AS?

NUONG MY THI TRUONG is the largest registered owner, with 100.0%.

What is the revenue of MYMY SUSHI AS?

MYMY SUSHI AS had revenue of NOK 1.9m in 2024.

Who is the general manager of MYMY SUSHI AS?

Nuong My Thi Truong is registered as general manager of MYMY SUSHI AS.

Where is MYMY SUSHI AS based?

MYMY SUSHI 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.