🚌 Weekly India Transit Grievance Redressal Audit

Window: 3 October 2026, 09:00 IST – 10 October 2026, 09:00 IST
Scope: The ten agencies in the configured watchlist; passenger grievances and visible agency replies on X. Searches used the configured current/history-handle patterns and agency search terms, then the required zero-result checks. X date filters are approximate; post-ID times were checked against the exact cutoff.
Result: 47 distinct complaints; 20 received a visible agency reply (43%); DTC reported completed staff warnings/counselling in three cases. Those corrective actions are agency-reported, not independently confirmed by the passengers; concessionaire penalties remain prospective. One headlight complaint is retained once as shared/unassigned TNSTC/SETC and excluded from both agency denominators. The median reply interval across 20 linked responses was about 5 hours 38 minutes.

Findings by agency

MTC Chennai — @MtcChennai

Complaints: 8 · Replies: 6 (75%) · Response time: about 4 minutes–3 hours 53 minutes; median about 27 minutes.
Categories: route/frequency (2), delay (2), staff conduct (1), safety/accessibility (1), fare/ticketing (1), other (1).

• Route 26 had a service gap followed by five buses arriving about two minutes apart. MTC said service was being monitored, instructions issued and promoted its app; no lasting fix is shown. Complaint · reply — ❌
• A Route 105 rider said live tracking was often missing or inaccurate. MTC replied that it was looking into the issue; no outcome followed. Complaint · reply — ❌
• Vandalur passengers reported waiting over an hour despite a 15-minute app estimate. MTC said it was looking into it. Complaint · reply — ❌
• Three other replied-to incidents concerned 6D delay, 147C bus bunching, and a 555S conductor stopping mid-route while issuing tickets. 6D complaint · reply; 147C complaint · reply; 555S complaint · reply — ❌
• No reply surfaced for a damaged, hanging CCTV unit near a driver’s bay or a passenger charged but issued a women’s free ticket. CCTV · ticket — ❌

CMRL Chennai Metro — @cmrlofficial

Complaints: 6 · Replies: 0 (0%) · Response time: none observed.
Categories: safety/accessibility (4), other (2).

Cases concerned blocked bike-parking access at St Thomas Mount, an incomplete Poonamallee–Vadapalani station entrance, a construction hazard, insufficient exits/parking at Thirumangalam, and unfinished gates affecting lift access at Annanagar East. The exit and parking reports are separate access problems. St Thomas Mount · Poonamallee–Vadapalani · construction · Thirumangalam exits · Thirumangalam parking · Annanagar East gates/lift — ❌. CMRL’s own notice about a temporary QR-ticketing glitch and its later fix was excluded as an official announcement, not a passenger grievance.

Chennai Suburban & MRTS — @DrmChennai

Complaints: 1 · Replies from Chennai Division: 0 (0%) · Response time: none from the division.

A Gummidipoondi–Chennai Central train was reported an hour late. RailwaySeva referred the passenger to RailMadad/139; it is not a Chennai Division reply. Separate posts about a derailment were news/incident reports, not passenger grievances, and were excluded. Complaint · RailwaySeva reply — ❌

CUMTA — @CumtaOfficial

Complaints: 0 · Replies: 0 · Response rate: N/A.

The zero-result check found a broad, angry post about CUMTA parking enforcement and spending, but no specific passenger incident or service failure; it was excluded under the config’s specificity rule. Excluded post

TNSTC (statewide) — shared candidate account @tnstc_setc

Complaints attributed: 2 · Replies: 0 (0%). Categories: delay (1), fare/ticketing (1).

One rider reported a Tiruvannamalai–Hosur trip taking 4h15 over 160 km. Another reported a Chennai–Krishnagiri bus non-arrival and pending refund, tagging @arasubus and using #TNSTC; operator attribution is unverified. No personal booking details are reproduced. Slow journey · non-arrival/refund — ❌

SETC — shared candidate account @tnstc_setc

Complaints attributed: 0 · Replies: 0 · Response rate: N/A.

One post tagged the joint candidate account about a bus operating without headlights, but identified neither operator nor route. It is recorded once as shared/unassigned, not counted under either agency. Shared case — ❌. A separate SETC delay post at about 07:46 IST on 3 October was before the 09:00 start and was excluded.

BEST Mumbai — @myBESTBus

Complaints: 5 · Replies: 0 (0%). Categories: delay (4), other (1).

Two distinct Route 252 service incidents were reported on successive days, including a missed 9:00 PM departure and unavailable live tracking; separate reports concerned Route 181 delays and a 51-minute Route 405 wait against an 18-minute schedule. A passenger also reported no update after reporting lost property on bus A286. Route 252 missed trip · Route 252 tracking/delay · Route 181 · Route 405 · lost property — ❌

BMTC Bengaluru — @BMTC_BENGALURU

Complaints: 12 · Replies: 8 (67%) · Response time: about 48 minutes–20 hours 23 minutes; median about 11 hours 16 minutes.
Categories: staff conduct (4), safety/accessibility (4), route/frequency (1), other (3).

Eight visible docket replies matched complaints; all acknowledge registration and do not confirm a fix. Replied-to issues included a driver using a phone, bus-stop refusals/skips, a driver leaving a bus on the road, an alleged bus/bike collision, missing route-tracking data, and two underspecified image-led posts. The vague posts are flagged unverified; BMTC itself acknowledged them as complaints. Driver phone / docket · bus-stop refusal / docket · repeated stop-skipping / docket · road obstruction / docket · reported collision / docket · tracking data / docket · vague road-access post / docket · media-only case / docket — ❌

Four other distinct cases had no BMTC reply: no Bannerghatta Road buses at the airport; a dangerous-driving complaint with video; a private car obstructing a BMTC bus stand; and a bus U-turn causing traffic chaos. Airport service · dangerous-driving thread / follow-up · bus-stand obstruction · U-turn — ❌. General lane-discipline questions and a dead tree near a depot were not counted as specific BMTC service failures.

DTC Delhi — @dtchq_delhi

Complaints: 12 · Replies: 6 (50%) · Response time: about 37 minutes–3 days 19 hours 53 minutes; median about 21 hours 5 minutes.
Categories: staff conduct (8), fare/ticketing (4).

Eight staff/stop cases involved drivers failing to stop or pick up passengers, unsafe driving, or road obstruction. Six received replies: R.K. Puram / reply ✅; Govindpuri / reply ✅; Route 539 case and reply ✅; Tilak Nagar / reply ❌; Vikas Puri / reply ❌. Three stop-skipping cases had no matched reply: IOCL stand, DAV School stand, Adchini. Four pass cases concerned a student payment stuck, a debit without pass generation, an undelivered printed pass, and a refund: payment stuck · pass not generated · pass not delivered · refund complaint / refund reply ❌. DTC says crew were identified, warned and counselled in the three ✅ cases; concessionaire penalties remain prospective. The Tilak Nagar and Vikas Puri replies only describe review/investigation, while the refund was promised but not confirmed paid.

KSRTC Kerala — @keralasrtc

Complaints: 0 · Replies: 0 · Response rate: N/A.

The zero-result check found one detailed bus-change/boarding complaint posted at about 06:15 IST on 3 October, before the audit’s 09:00 IST start; it was excluded from this window. No qualifying in-window complaint was found. Out-of-window post

City/system summary

• Most responsive: MTC, 6/8 (75%); DTC’s three reported crew warnings/counselling actions are the strongest outcomes, though passengers have not independently confirmed them.
• City totals: Chennai 15 complaints/6 replies; Bengaluru 12/8; Delhi 12/6; Mumbai 5/0; Tamil Nadu intercity 2/0 plus one shared/unassigned/0; Kerala 0.
• Least responsive among agencies with complaints: CMRL (0/6) and BEST (0/5); both had no visible agency reply.
• Top category: staff conduct (13), followed by safety/accessibility (9) and delay (8).
• Total: 47 distinct complaints, including one shared/unassigned TNSTC/SETC case; 20 got a visible agency reply (43%); DTC reported corrective crew warnings/counselling in 3 cases, with concessionaire penalties still prospective and no independent passenger confirmation.
• Best response: DTC’s R.K. Puram, Govindpuri and Route 539 replies report that crews were identified, warned and counselled; penalties are still prospective and the action is not independently verified by the passengers.
• Needs improvement: CMRL and BEST had six and five complaints respectively, with no visible agency response.
• Open issues: BMTC’s docketed driver-safety cases have no public outcomes; DTC’s pass/refund cases have no confirmation of issuance/payment, and concessionaire penalties are still pending.

Detection review and update

• Corrected the Chennai Division handle to @DrmChennai and CUMTA to @CumtaOfficial; retained the old values in handle_history. The old Chennai Division handle did not resolve; the CUMTA profile identifies itself as the authority and is referenced by Chennai One.
• Replaced inactive TNSTC/SETC entries with the shared candidate @tnstc_setc. Its bio describes both corporations, but no government-site link independently verified its official status. The config now requires shared incidents to be counted once and leaves operator attribution explicit.
• Added agency-specific broad search terms, including MTC tracking and MTC live tracking, after name searches surfaced an untagged Route 105 tracking grievance and a TNSTC slow-service complaint. The official Chennai Metro ticketing-glitch notice/fix and suburban derailment news posts were excluded because they were not passenger grievances. No new category was needed; existing categories cover the new issues.
• Generic CUMTA criticism, an old BMTC allegation referring to 1980, a general lane-change question, praise, official posts and pre-window complaints were excluded. BMTC image-led cases are flagged unverified only where BMTC itself acknowledged a complaint.
• Updated detection config to v1.2; all 13 labeled complaint cases retained their expected agency/category labels, and all 3 known-miss drills remained intact. No hourly scheduler data was included.

Method and limits

Counts are distinct incidents surfaced by the configured current/history handle patterns and agency search terms. Follow-ups were merged; repeated Route 252 departures on separate days were kept as separate service incidents. The joint TNSTC/SETC headlight issue was counted once and left unassigned because the post does not name an operator. Replies are counted only when visible and tied to a surfaced complaint. Dockets, apologies, referrals and promised refunds count as replies, not resolutions; DTC’s stated warnings/counselling are marked ✅ as agency-reported corrective actions, not independent passenger confirmation. Response times are approximate intervals decoded from X post IDs. This is an X-visible sample, not a count of all complaints received by agencies; deleted posts, DMs and private conversations are not visible.

Detection sources: config · methodology · changelog · evaluation set