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

SUN SUSHI AS

Org. no. 916942141 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK −439
Equity NOK −362,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

SUN SUSHI AS is registered as a limited company in Oslo, Oslo with organisation number 916942141. 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 100 shares. The company's stated purpose is: “Take-away av sushi-retter + brus.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK −439 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK −439
Equity
NOK −362,000

Financial health · 2024

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

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

Who owns SUN SUSHI AS?

THI THU LANG NGUYEN
SUN SUSHI AS
NOK 2.7m rev. · NOK −439 profit

SUN SUSHI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SUN SUSHI AS

Who owns SUN SUSHI AS?

THI THU LANG NGUYEN is the largest registered owner, with 50.0%.

What is the revenue of SUN SUSHI AS?

SUN SUSHI AS had revenue of NOK 2.7m in 2024.

Who is the general manager of SUN SUSHI AS?

Loi Van Phan is registered as general manager of SUN SUSHI AS.

Where is SUN SUSHI AS based?

SUN 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.