Garib Rath Express: punctuality report, Sept 29 to Oct 5
Which Garib Rath trains ran on time this week. Average peak delays up to 295 minutes; on-time rate 26% (within 15 minutes).
TrainLiveStatus Desk · Updated · 3 min read
This report covers 29 September to 5 October 2026 (7 days) and 47 Garib Rath trains in the TrainLiveStatus delay history. For each train and day we take the largest delay reported during that day's run. A day counts as on time if that largest delay was within 15 minutes. Across all trains the average peak delay was 68 minutes and the on-time rate was 26%. We ranked 19 trains.
Worst performers this week
The 12201 TVCN Garibrath (Lokmanyatilak to Thiruvananthapuram North) had the hardest week, with an average peak delay of 295 minutes across three observed days and a worst day of 440 minutes. None of those days was on time.
The 12203 Garib Rath Express (Saharsa to Amritsar) averaged 197 minutes over five observed days. One of the five days was on time, the median was 44 minutes, and the worst day was 718 minutes (almost 12 hours), which is why the average is so much higher than the median. Our data shows it regained 139 minutes on average after its peak.
The 22405 ANVT Garib Rath (Bhagalpur to Anand Vihar Terminal) has three observed days and three cancelled days in our data this week. On the days it ran it averaged 171 minutes of delay, with a worst day of 288 minutes.
The 12877 NDLS Garib Rath (Ranchi to New Delhi) averaged 110 minutes over four observed days with no on-time days, and regained 40 minutes on average. The 12204 SHC Garib Rath (Amritsar to Saharsa) averaged 89 minutes over five days with none on time.
Better performers
The 12215 BDTS Garib Rath (Delhi Sarai Rohilla to Bandra Terminus) had the lowest average peak delay of the trains listed here, at 19 minutes, with 50% of observed days on time across six days.
The 12910 BDTS Garibrath (Hazrat Nizamuddin to Bandra Terminus) was on time on 67% of its six observed days, with an average peak delay of 28 minutes. The 12536 R LJN Garibrath (Raipur to Lucknow) was on time on 25% of four observed days and averaged 68 minutes, which was in the middle of the ranking.
What these numbers mean
An average peak delay of 68 minutes means that across all tracked Garib Rath trains the worst point of a day's run was, on average, a little over an hour behind schedule. The 26% on-time rate shows that most days had a peak delay above 15 minutes. This is a one-week snapshot and says nothing about the causes.
If you are planning to use a Garib Rath train, check the live running status and the delay history on the train's page before you leave for the station. That is more useful than the scheduled time when you are planning a connection or a pickup.
How to interpret this data
This report uses the largest delay reported during each train's run on each day it was observed. On time means that largest delay was within 15 minutes. These are our own figures, not an official measure. Trains that run only a few days a week have fewer observed days, so their averages rest on small samples. They help show which trains are often late and which regain time, not to predict an arrival to the minute.
For delays that affect your connection, use the trip planner to look at alternate stations and two-train connections, or read how to understand a train's punctuality before booking.
More reports
See also the most delayed trains of the previous week and the Rajdhani punctuality report.
Use it on your trip
Frequently asked questions
Why is the average delay different from the worst delay?
The average peak delay is the mean of the largest delay recorded on each observed day. A single very bad day, such as 718 minutes for the 12203, pulls the average up well above the median.
If a train regained time, why does it show a large delay?
We report the largest delay during the run, not the delay at the destination. A train that was 440 minutes late at its worst point may have reached its destination with a smaller delay.
Should I avoid Garib Rath trains because of these delays?
Not necessarily. Some, like the 12910 and 12215, were on time on half or more of their observed days this week. Check the live status and delay history of your specific train and use the trip planner to look at alternatives.
What counts as on time in this report?
A day counts as on time if the largest delay reported during that day's run was within 15 minutes. This is the threshold we chose for this report.
Were any Garib Rath trains cancelled this week?
Yes, in our data the 22405 (Bhagalpur to Anand Vihar Terminal) had three cancelled days and the 22406 (Anand Vihar Terminal to Bhagalpur) had one. Cancelled days are not counted in the delay averages.
Can I use this to predict my train's delay?
No. This is a one-week snapshot and delays change from week to week. Check the live running status for your train's current delay.
Sources
Rules and fares change. Check the official source before you travel. Last reviewed 5 October 2026.
