biztrac. BETA
COMPANY REGISTER PROFILE
916139195 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

WASABI SUSHI DRAMMEN AS

Org. no. 916139195 Limited company (AS) Drammen Incorporated 2015 Active
Revenue 2025 NOK 8.4m
Operating profit NOK 643,000
Equity NOK 522,000
Incorporated 2015
Employees 13
Share capital NOK 30,000

WASABI SUSHI DRAMMEN AS is registered as a limited company in Drammen, Buskerud with organisation number 916139195. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Sushibar og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK 643,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
▲ +5 %
Operating profit
NOK 643,000
▲ +4 %
Equity
NOK 522,000
▲ +13 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
42.8%
Very good
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns WASABI SUSHI DRAMMEN AS?

WASABI SUSHI DRAMMEN AS
NOK 8.4m rev. · NOK 643,000 profit

WASABI SUSHI DRAMMEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about WASABI SUSHI DRAMMEN AS

Who owns WASABI SUSHI DRAMMEN AS?

Thi Ai Do is the largest registered owner, with 34.0%.

What is the revenue of WASABI SUSHI DRAMMEN AS?

WASABI SUSHI DRAMMEN AS had revenue of NOK 8.4m in 2025.

Who is the general manager of WASABI SUSHI DRAMMEN AS?

Thi Ai Do is registered as general manager of WASABI SUSHI DRAMMEN AS.

Where is WASABI SUSHI DRAMMEN AS based?

WASABI SUSHI DRAMMEN AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.