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

GREVERUD SUSHI & WOK AS

Org. no. 914042089 Limited company (AS) Nordre Follo Incorporated 2014 Active
Revenue 2025 NOK 5.2m
Operating profit NOK 694,000
Equity NOK 1.1m
Incorporated 2014
Share capital NOK 30,000

GREVERUD SUSHI & WOK AS is registered as a limited company in Nordre Follo, Akershus with organisation number 914042089. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Sushibar og deltakelse i andre virksomhet av samme karakter.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 694,000 in operating profit.

Former names: OSLO SUSHI AS

Key figures · 2025

Revenue
NOK 5.2m
▲ +4 %
Operating profit
NOK 694,000
▼ −10 %
Equity
NOK 1.1m
▲ +89 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
2.00
Good
Current assets ÷ current liabilities
Profitability
44.6%
Very good
Return on total assets
Solidity
73.8%
Very good
Equity as a share of total capital

Who owns GREVERUD SUSHI & WOK AS?

GREVERUD SUSHI & WOK AS
NOK 5.2m rev. · NOK 694,000 profit

GREVERUD SUSHI & WOK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GREVERUD SUSHI & WOK AS

Who owns GREVERUD SUSHI & WOK AS?

Trang Thi Thu Nguyen is the largest registered owner, with 100.0%.

What is the revenue of GREVERUD SUSHI & WOK AS?

GREVERUD SUSHI & WOK AS had revenue of NOK 5.2m in 2025.

Who is the general manager of GREVERUD SUSHI & WOK AS?

Trang Thi Thu Nguyen is registered as general manager of GREVERUD SUSHI & WOK AS.

Where is GREVERUD SUSHI & WOK AS based?

GREVERUD SUSHI & WOK AS has its business address in Oppegård.

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.