Brother Runs the Vendor—Nephew Signs the Bills—Uncle Draws the Salary

In RVNL, Surviving Complaints Is a Qualification for Promotion

A #Railwhispers Investigation—Part I of II

This is the second time #Railwhispers is reporting on the deep-rooted culture of impunity within Rail Vikas Nigam Limited (#RVNL). Our first piece, published on 16 January 2026, documented how RVNL has effectively functioned as a patronage machine—a system where retiring officers transition into a life of comfort funded by vehicles, manpower, and hospitality extracted from subordinates and vendors.

While that initial report drew on systemic observations, this installment is built on a formal, documented complaint addressed to RVNL’s Chairman and Managing Director (#CMD) and corroborated by multiple independent sources. Read together, these two pieces expose a system where #Corruption is not an aberration, but the standard operating procedure.

The formal complaint filed with the CMD/RVNL alleges that a senior officer—referred to here as “A”—has systematically constructed a family-controlled financial ring within a government infrastructure project. The complaint details how “A” used his official position to sustain this ring, secured protection from senior executives by providing them with vehicles and services, and has now been promoted to Deputy General Manager—despite a long trail of prior complaints that were suppressed rather than investigated.

This complaint is exceptionally specific. It cites exact GST registration numbers, vehicle license plates, and internal RVNL correspondence by letter number and date. It also explicitly names the project: the Janghai-Phaphamau electrification project under GGM/Electrical/Varanasi. These are not anonymous, baseless allegations flung into the air; they are verifiable claims that can be checked against public records and internal RVNL documentation. The only question that remains is whether anyone in authority possesses the political will to verify them.

The Architecture of the Arrangement

The complaint describes a closed-loop structure designed to ensure complete control. Every single stage of this financial pipeline is managed by a relative of “A”.

‘A’s brother—referred to here as “B”—is the registered proprietor of a #vendor firm operating under GST number 09AHXPV9972C1Z8. The #complaint alleges that this firm was specifically used to process bills for the exact project under “A’s” official charge. The familial tie between “A” and “B” is easily verifiable through PAN card records, which reveal identical father’s names.

Meanwhile, ‘A’s nephew—referred to here as “C”—was allegedly appointed as Supervisor (Civil) through ‘A’s direct influence. ‘C’s role in this network is structural, not incidental. The bills generated by ‘B’s vendor firm are reportedly verified and approved by “C”. In short, the individual creating the invoices and the individual approving them are brothers and nephews of the officer overseeing the entire project. This transcends a mere conflict of interest; it is a family business operating inside a public sector enterprise under the shield of official designations.

A fourth figure—‘A’s driver, referred to here as “D”—is registered as the nominal owner of a second vehicle. However, the complaint alleges that this vehicle is effectively controlled by “A” and deployed for his personal financial benefit. The beneficial ownership and the recorded ownership have been deliberately separated to obfuscate the paper trail.

The Vehicle Fraud: Numbers That Tell the Story

The complaint outlines an elaborate vehicle billing scheme. One specific vehicle, registration number UP32JF3832, was reportedly attached to “A” from October 2017 onward. According to the documentation, it has remained continuously attached on paper for billing purposes across multiple successive projects.

When the vehicle’s odometer crossed the 1.5 lakh kilometer threshold—a point that normally triggers bureaucratic scrutiny for replacement—the odometer was allegedly rolled back to approximately 25,000 to 30,000 kilometers. This tampering rendered the vehicle eligible on paper for billing in the next project cycle.

Furthermore, the complaint notes that the vehicle’s insurance lapsed in 2024, and it currently carries eight pending traffic challans (fines). The complainant argues this is undeniable proof that the vehicle had effectively ceased operating on public roads after 2024, making any subsequent billing flagrantly fraudulent.

The second vehicle, registered under ‘D’s name, operates on the exact same principle: nominal ownership divorced from actual control, with billing processed to funnel public funds straight into ‘A’s personal network.

Through these combined vehicle scams, the complaint estimates that approximately Rs. 1.5 lakh per month is being extracted in cash, routed through “B”, and continuously billed under legitimate RVNL works.

These claims are entirely verifiable. Vehicle registration records, odometer logs, maintenance histories, insurance renewal dates, and challan records are all readily accessible through the Ministry of Road Transport’s #VAHAN database and RVNL’s internal logs. The question, once again, is whether anyone will actually look.

Part-II of this investigation—“RVNL Did Not Fail to Notice—It Chose Not To”—will examine how “A” built and maintained his protection armor among senior executives, his role as a financial conduit for two senior railway officials, the documented suppression of prior complaints, and the exact scope a complete investigation must now cover.

The earlier article in this series was published on 16 January 2026 and can be read here: “RVNL का सराहनीय प्रयास—अब धूर्तों की खैर नहीं!”