BIZTRAC BETA
Restaurant activities

ÅLESUND SUSHI AS

Org. no. 917870012 Limited company (AS) Ålesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 16,000
Equity NOK −58,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

ÅLESUND SUSHI AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 917870012. 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: “Selskapets virksomhet er å produsere og selge sushi, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 16,000
Equity
NOK −58,000
Est. value
NOK 122,000

Financial health · 2025

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

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

Who owns ÅLESUND SUSHI AS?

HIEN VAN CAO
ÅLESUND SUSHI AS
NOK 1.6m rev. · NOK 16,000 profit

ÅLESUND SUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅLESUND SUSHI AS

Who owns ÅLESUND SUSHI AS?

HIEN VAN CAO is the largest registered owner, with 100.0%.

What is the revenue of ÅLESUND SUSHI AS?

ÅLESUND SUSHI AS had revenue of NOK 1.6m in 2025.

Where is ÅLESUND SUSHI AS based?

ÅLESUND SUSHI AS has its business address in Ålesund.

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.