BIZTRAC BETA
Restaurant activities

SUSHI TASTA AS

Org. no. 921280882 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 796,000
Equity NOK 547,000
Incorporated 2018
Employees 29
Share capital NOK 330,000

SUSHI TASTA AS is registered as a limited company in Stavanger, Rogaland with organisation number 921280882. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 29 registered employees. Registered share capital is NOK 330,000, divided into 1000 shares. The company's stated purpose is: “Fremstilling/salg av sushi og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet. Kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 796,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 796,000
Equity
NOK 547,000
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns SUSHI TASTA AS?

MADLAKROSSEN SUSHI AS
SUSHI TASTA AS
NOK 7.5m rev. · NOK 796,000 profit

SUSHI TASTA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SUSHI TASTA AS

Who owns SUSHI TASTA AS?

MADLAKROSSEN SUSHI AS is the largest registered owner, with 75.0%.

What is the revenue of SUSHI TASTA AS?

SUSHI TASTA AS had revenue of NOK 7.5m in 2024.

Who is the general manager of SUSHI TASTA AS?

Jan Gunnar Øvestad is registered as general manager of SUSHI TASTA AS.

Where is SUSHI TASTA AS based?

SUSHI TASTA AS has its business address in Stavanger.

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.