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

RICE BOWL AS

Org. no. 819063052 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 23.0m
Operating profit NOK 2.0m
Equity NOK 38,000
Incorporated 2017
Employees 22
Share capital NOK 30,000

RICE BOWL AS is registered as a limited company in Oslo, Oslo with organisation number 819063052. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 22 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av restaurant og kafeer. Salg av sunn og godt mat, varmmat og annet tilhørende produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.0m in revenue and NOK 2.0m in operating profit.

Former names: RICE BOWL WANTHAPHIROM AS

Key figures · 2025

Revenue
NOK 23.0m
▼ −8 %
Operating profit
NOK 2.0m
▼ −45 %
Equity
NOK 38,000
▼ −99 %
Est. value
NOK 8.4m

Financial health · 2025

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
39.2%
Very good
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns RICE BOWL AS?

RICE BOWL AS
NOK 23.0m rev. · NOK 2.0m profit

RICE BOWL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RICE BOWL AS

Who owns RICE BOWL AS?

Suradeth Wantapirom is the largest registered owner, with 100.0%.

What is the revenue of RICE BOWL AS?

RICE BOWL AS had revenue of NOK 23.0m in 2025.

Who is the general manager of RICE BOWL AS?

Suradeth Wantapirom is registered as general manager of RICE BOWL AS.

Where is RICE BOWL AS based?

RICE BOWL 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.