Company record (for your files)

ENGINEERING DIVISION S.R.L.

CUI 41084653 · J2019006147408 · Bucureşti Sectorul 1, Bucureşti · founded 2019

Registry date (ONRC): 4 November 2026 (firme-04-11-2026) · Generated: 14 November 2026, 02:47 (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)yes
Financial health score98 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.
Revenue3,948,458 RON (in 2025)
Net profit2,501,067 RON

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

Follow this company Check another company

Identity

NameENGINEERING DIVISION S.R.L.
CUI41084653
Registration no.J2019006147408
Legal formSRL
Registered on9 May 2019
AddressGheorghe Ionescu Siseşti no. 144B, Sector 1, Bucureşti, postcode 013824
Main activity (CAEN)7112 Activități de inginerie și consultanță tehnică legate de acestea
e-Facturanot registered in the RO e-Factura register
Directorsin the app, after signing in →
Details
EUIDROONRC.J2019006147408

Latest filing

Year2025
Revenue3,948,458 RON
Net profit/loss2,501,067 RON
Employees6
Total assets4,444,610 RON
Liabilities1,899,656 RON
Equity2,503,467 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 record401e17a6e8b52ffad1407be2f57e1f1b9240df3a11a5f811d003ce9c4cbc569f
Stable URLhttps://leadgen.adrianhomelab.com/record/41084653?snapshot=firme-04-11-2026

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