BIZTRAC BETA
COMPANY REGISTER PROFILE
923244409 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

PEARLIS SUSHI GODBIT AS

Org. no. 923244409 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 25,000
Equity NOK 529,000
Incorporated 2019
Employees 5
Share capital NOK 30,000

PEARLIS SUSHI GODBIT AS is registered as a limited company in Oslo, Oslo with organisation number 923244409. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant og kafeer, baguetter og bubbletea.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 25,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 25,000
Equity
NOK 529,000
Est. value
NOK 328,000

Financial health · 2024

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

Who owns PEARLIS SUSHI GODBIT AS?

XUAN DIEU THI VAN
PEARLIS SUSHI GODBIT AS
NOK 3.9m rev. · NOK 25,000 profit

PEARLIS SUSHI GODBIT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEARLIS SUSHI GODBIT AS

Who owns PEARLIS SUSHI GODBIT AS?

XUAN DIEU THI VAN is the largest registered owner, with 100.0%.

What is the revenue of PEARLIS SUSHI GODBIT AS?

PEARLIS SUSHI GODBIT AS had revenue of NOK 3.9m in 2024.

Who is the general manager of PEARLIS SUSHI GODBIT AS?

Xuan Dieu Thi Van is registered as general manager of PEARLIS SUSHI GODBIT AS.

Where is PEARLIS SUSHI GODBIT AS based?

PEARLIS SUSHI GODBIT AS has its business address in Oslo.

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.