BIZTRAC BETA
Restaurant activities

BROR SUSHI AS

Org. no. 911607344 Limited company (AS) Time Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 9.3m
Operating profit NOK 1.1m
Equity NOK 582,000
Incorporated 2013
Employees 11
Share capital NOK 60,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BROR SUSHI AS is registered as a limited company in Time, Rogaland with organisation number 911607344. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013 and has 11 registered employees. Registered share capital is NOK 60,000, divided into 30000 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 9.3m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 9.3m
Operating profit
NOK 1.1m
Equity
NOK 582,000
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns BROR SUSHI AS?

ORSTAD RÅDGIVNING AS
BROR SUSHI AS
NOK 9.3m rev. · NOK 1.1m profit

BROR SUSHI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROR SUSHI AS

Who owns BROR SUSHI AS?

ORSTAD RÅDGIVNING AS is the largest registered owner, with 100.0%.

What is the revenue of BROR SUSHI AS?

BROR SUSHI AS had revenue of NOK 9.3m in 2024.

Where is BROR SUSHI AS based?

BROR SUSHI AS has its business address in Bryne.

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.