BIZTRAC BETA
Restaurant activities

SÆTRE SUSHI & WOK AS

Org. no. 925146064 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 38,000
Equity NOK 394,000
Incorporated 2020
Employees 6
Share capital NOK 30,000

SÆTRE SUSHI & WOK AS is registered as a limited company in Asker, Akershus with organisation number 925146064. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drifter av spisested. Salg av sunn og godt mat, sushi, og annet tilhørende produkter. Butikkhandel med bredt vareutvalg med hovedvekt på nærings- og nytelsesmidler.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 38,000
Equity
NOK 394,000
Est. value
NOK 370,000

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.3%
Very good
Equity as a share of total capital

Who owns SÆTRE SUSHI & WOK AS?

THAI BINH NGUYEN
SÆTRE SUSHI & WOK AS
NOK 2.7m rev. · NOK 38,000 profit

SÆTRE SUSHI & WOK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SÆTRE SUSHI & WOK AS

Who owns SÆTRE SUSHI & WOK AS?

THAI BINH NGUYEN is the largest registered owner, with 100.0%.

What is the revenue of SÆTRE SUSHI & WOK AS?

SÆTRE SUSHI & WOK AS had revenue of NOK 2.7m in 2025.

Who is the general manager of SÆTRE SUSHI & WOK AS?

Thai Binh Nguyen is registered as general manager of SÆTRE SUSHI & WOK AS.

Where is SÆTRE SUSHI & WOK AS based?

SÆTRE SUSHI & WOK AS has its business address in Sætre.

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.