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

SUSHIWOKEKSPRESSEN AS

Org. no. 917135495 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 36,000
Equity NOK 400,000
Incorporated 2016
Share capital NOK 50,000

SUSHIWOKEKSPRESSEN AS is registered as a limited company in Oslo, Oslo with organisation number 917135495. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Godt utvalg av sushi, sunne asiatiske varm matretter og take away og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 36,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 36,000
Equity
NOK 400,000
Est. value
NOK 380,000

Financial health · 2024

Liquidity
1.78
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
57.3%
Very good
Equity as a share of total capital

Who owns SUSHIWOKEKSPRESSEN AS?

HA TRIEU NGUYEN CAO
SUSHIWOKEKSPRESSEN AS
NOK 3.2m rev. · NOK 36,000 profit

SUSHIWOKEKSPRESSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUSHIWOKEKSPRESSEN AS

Who owns SUSHIWOKEKSPRESSEN AS?

HA TRIEU NGUYEN CAO is the largest registered owner, with 100.0%.

What is the revenue of SUSHIWOKEKSPRESSEN AS?

SUSHIWOKEKSPRESSEN AS had revenue of NOK 3.2m in 2024.

Who is the general manager of SUSHIWOKEKSPRESSEN AS?

Ha Trieu Nguyen Cao is registered as general manager of SUSHIWOKEKSPRESSEN AS.

Where is SUSHIWOKEKSPRESSEN AS based?

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