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

LØKEN SUSHI & WOK AS

Org. no. 833920952 Limited company (AS) Aurskog-Høland Incorporated 2024 Active
Revenue 2025 NOK 2.5m
Operating profit NOK 45,000
Equity NOK 70,000
Incorporated 2024
Employees 5
Share capital NOK 30,000

LØKEN SUSHI & WOK AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 833920952. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av restauranter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 45,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▲ +162 %
Operating profit
NOK 45,000
▲ +1039 %
Equity
NOK 70,000
▲ +112 %
Est. value
NOK 179,000

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
19.9%
Very good
Return on total assets
Solidity
26.8%
Weak
Equity as a share of total capital

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

Who owns LØKEN SUSHI & WOK AS?

LØKEN SUSHI & WOK AS
NOK 2.5m rev. · NOK 45,000 profit

LØKEN SUSHI & WOK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØKEN SUSHI & WOK AS

Who owns LØKEN SUSHI & WOK AS?

Son Ca Nguyen Hoang is the largest registered owner, with 100.0%.

What is the revenue of LØKEN SUSHI & WOK AS?

LØKEN SUSHI & WOK AS had revenue of NOK 2.5m in 2025.

Who is the general manager of LØKEN SUSHI & WOK AS?

Son Ca Nguyen Hoang is registered as general manager of LØKEN SUSHI & WOK AS.

Where is LØKEN SUSHI & WOK AS based?

LØKEN SUSHI & WOK AS has its business address in Løken.

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.