BIZTRAC BETA
Restaurant activities

TORINO’S RESTAURANT & BAR AS

Org. no. 935003504 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 2.2m
Operating profit NOK 64,000
Equity NOK 81,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

TORINO’S RESTAURANT & BAR AS is registered as a limited company in Ringerike, Buskerud with organisation number 935003504. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive bar- og restaurantvirksomhet, samt annet som naturlig står i den forbindelse.”.

Key figures

Revenue
NOK 2.2m
Operating profit
NOK 64,000
Equity
NOK 81,000
Est. value
NOK 279,000

Financial health · 2025

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

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

Who owns TORINO’S RESTAURANT & BAR AS?

FARMAN MAHMOUD SALMAN
TORINO’S RESTAURANT & BAR AS
NOK 2.2m rev. · NOK 64,000 profit

TORINO’S RESTAURANT & BAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORINO’S RESTAURANT & BAR AS

Who owns TORINO’S RESTAURANT & BAR AS?

FARMAN MAHMOUD SALMAN is the largest registered owner, with 100.0%.

What is the revenue of TORINO’S RESTAURANT & BAR AS?

TORINO’S RESTAURANT & BAR AS had revenue of NOK 2.2m.

Who is the general manager of TORINO’S RESTAURANT & BAR AS?

Farman Mahmoud Salman is registered as general manager of TORINO’S RESTAURANT & BAR AS.

Where is TORINO’S RESTAURANT & BAR AS based?

TORINO’S RESTAURANT & BAR AS has its business address in Hønefoss.

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.