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

SLEMDAL SUSHI & GRILL AS

Org. no. 923077928 Limited company (AS) Nesodden Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 17,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).
  • Nylig endring 2026-05-05 Adresseendring registrert 2026-05-05.

SLEMDAL SUSHI & GRILL AS is registered as a limited company in Nesodden, Akershus with organisation number 923077928. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift, herunder servering av mat og drikke, samt annen virksomhet som naturlig faller sammen med dette.”.

Former names: RIVILE AS

Key figures · 2025

Operating profit
NOK −21,000
Equity
NOK 17,000
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns SLEMDAL SUSHI & GRILL AS?

RIMVYDAS BALANDIS
SLEMDAL SUSHI & GRILL AS
· NOK −21,000 profit

SLEMDAL SUSHI & GRILL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLEMDAL SUSHI & GRILL AS

Who owns SLEMDAL SUSHI & GRILL AS?

RIMVYDAS BALANDIS is the largest registered owner, with 100.0%.

Who is the general manager of SLEMDAL SUSHI & GRILL AS?

Hasib Ullah Arefzada is registered as general manager of SLEMDAL SUSHI & GRILL AS.

Where is SLEMDAL SUSHI & GRILL AS based?

SLEMDAL SUSHI & GRILL AS has its business address in Fjellstrand.

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.