Company record (for your files)

LECHPOL ELECTRONIC SRL

CUI 22976532 · J2007001142113 · Municipiul Reşiţa, Caraş-Severin · founded 2007

Registry date (ONRC): 4 November 2026 (firme-04-11-2026) · Generated: 12 November 2026, 06:29 (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 score81 out of 100 – strong
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.
Revenue40,756,164 RON (in 2025)
Net profit1,935,553 RON

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

Follow this company Check another company

Identity

NameLECHPOL ELECTRONIC SRL
CUI22976532
Registration no.J2007001142113
Legal formSRL
Registered on20 December 2007
AddressB-dul Republicii, Municipiul Reşiţa, Caraş-Severin County
Main activity (CAEN)4650 Comerț cu ridicata al echipamentului informatic și de telecomunicații
e-Facturanot registered in the RO e-Factura register
Directorsin the app, after signing in →
Details
EUIDROONRC.J2007001142113

Latest filing

Year2025
Revenue40,756,164 RON
Net profit/loss1,935,553 RON
Employees31
Total assets24,076,679 RON
Liabilities7,137,794 RON
Equity16,795,559 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 recordf884268d105af99e92325b54a34184e26662e5686f87e6ef4a00ccbeed869785
Stable URLhttps://leadgen.adrianhomelab.com/record/22976532?snapshot=firme-04-11-2026

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