BIZTRAC BETA
Restaurant activities

EL-TORO AS

Org. no. 922937117 Limited company (AS) Haugesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK −117,000
Equity NOK −338,000
Incorporated 2019
Employees 9
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−338k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−117k kr).

EL-TORO AS is registered as a limited company in Haugesund, Rogaland with organisation number 922937117. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av gatekjøkken, samt virksomhet som naturlig står i forbindelse med dette og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK −117,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
Operating profit
NOK −117,000
Equity
NOK −338,000

Financial health · 2025

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

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

Who owns EL-TORO AS?

SIMOUN CHKRO
EL-TORO AS
NOK 8.9m rev. · NOK −117,000 profit

EL-TORO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EL-TORO AS

Who owns EL-TORO AS?

SIMOUN CHKRO is the largest registered owner, with 100.0%.

What is the revenue of EL-TORO AS?

EL-TORO AS had revenue of NOK 8.9m in 2025.

Who is the general manager of EL-TORO AS?

Simoun Chkro is registered as general manager of EL-TORO AS.

Where is EL-TORO AS based?

EL-TORO AS has its business address in Haugesund.

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.