BIZTRAC BETA
Restaurant activities

FETSUND SUSHI OG WOK AS

Org. no. 928232778 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 381,000
Equity NOK 324,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FETSUND SUSHI OG WOK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 928232778. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Serverings- og cateringvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 381,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 381,000
Equity
NOK 324,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.6%
Good
Equity as a share of total capital

Who owns FETSUND SUSHI OG WOK AS?

BUI HOLDING AS
FETSUND SUSHI OG WOK AS
NOK 4.4m rev. · NOK 381,000 profit

FETSUND SUSHI OG WOK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FETSUND SUSHI OG WOK AS

Who owns FETSUND SUSHI OG WOK AS?

BUI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FETSUND SUSHI OG WOK AS?

FETSUND SUSHI OG WOK AS had revenue of NOK 4.4m in 2024.

Who is the general manager of FETSUND SUSHI OG WOK AS?

Johnny Bui is registered as general manager of FETSUND SUSHI OG WOK AS.

Where is FETSUND SUSHI OG WOK AS based?

FETSUND SUSHI OG WOK AS has its business address in Fetsund.

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.