Company record (for your files)

ISTY&LEVY SRL

CUI 24178103 · J2008001277269 · Sat Band, Comuna Band, Mureş · founded 2008

Registry date (ONRC): 4 November 2026 (firme-04-11-2026) · Generated: 13 November 2026, 10:46 (Romanian time)

At a glance

Signals checked: registry status (ONRC), tax inactivity (ANAF), latest accounts. Not checked: the insolvency bulletin (BPI); debts to the state budget (ANAF).

StatusActive
Tax status (ANAF)Fiscally active
VAT payeryes
Cash-accounting VAT (TVA la încasare)no
Financial health score49 out of 100 – watch
The score (0–100) combines profitability, profit record, solvency, liquidity, growth and how steadily accounts are filed: above 55 the company is healthy, below 35 it is weak.
Revenue5,336,181 RON (in 2025)
Net profit9,484 RON

Data updated 9 November 2026 · Sources: ONRC, ANAF, Ministry of Finance

Follow this company Check another company

Identity

NameISTY&LEVY SRL
CUI24178103
Registration no.J2008001277269
Legal formSRL
Registered on10 July 2008
AddressStr. Targu Muresului no. 36, Sat Band, Comuna Band, Mureş County
Main activity (CAEN)4711 Comerț cu amănuntul în magazine nespecializate, cu vânzare predominantă de produse alimentare, băuturi și tutun
e-Facturanot registered in the RO e-Factura register
Directorsin the app, after signing in →
Details
EUIDROONRC.J2008001277269

Latest filing

Year2025
Revenue5,336,181 RON
Net profit/loss9,484 RON
Employees30
Total assets4,138,771 RON
Liabilities2,986,540 RON
Equity658,089 RON

See the 18-year history and health score — free with your email

Risk: no signals (active company)

No signal in the data above.

Sources

Are you in the registry?

Not checked by Leadgen

the insolvency bulletin (BPI); debts to the state budget (ANAF); court cases; shareholders and beneficial owners.

For developers

Download JSON

Integrity

SHA-256 of the recorddf828844dbced438b3b6c9263b5cfaad968c8d315d62477abcd22ed41d12bc6b
Stable URLhttps://leadgen.adrianhomelab.com/record/24178103?snapshot=firme-04-11-2026

The hash covers the JSON record (?format=json) without its integrity and generatedAt fields.