Amrit Bharat delays, 30 Oct to 5 Nov 2026: our tracking
How 23 Amrit Bharat trains ran from 30 October to 5 November 2026 in our own delay tracking: largest daily delay, on-time share and days observed.
TrainLiveStatus Desk · Updated · 4 min read
What we measured and how
This report uses only TrainLiveStatus's own delay tracking for the seven days from 30 October to 5 November 2026. For each train we record the largest delay reported during that day's run. A train counts as on time on a day when that largest delay is within 15 minutes.
This is our own tracking, not an official Indian Railways statistic. We saw 86 Amrit Bharat trains in this window, and 23 had enough reports to be ranked. Across those 23 trains the average largest daily delay was 126 minutes, and 6% of observed train-days were on time as we count it. Railway zones publish their own figures, which can differ from ours.
The 15 most delayed Amrit Bharat trains
Trains are ranked by their average largest daily delay. The table shows the top 15 of the 23 ranked trains. "Days seen" is the number of days in the window for which we had a report for that train, and "Runs on" comes from our timetable.
| # | Train | Route | Runs on | Days seen | Average largest delay | Worst day | On time |
|---|---|---|---|---|---|---|---|
| 1 | Amrit Bharat Express (14663) | New Jalpaiguri to Amritsar | Sat | 3 of 7 | 10 h 05 min | 11 h 56 min | 0% |
| 2 | CBE DHN Amrit BH (22364) | Coimbatore Jn to Dhanbad Jn | Tue | 3 of 7 | 4 h 54 min | 5 h 47 min | 0% |
| 3 | Amrit Bharat (16602) | Jogbani to Erode Jn | Sun | 3 of 7 | 3 h 45 min | 10 h 12 min | 0% |
| 4 | APDJ Amritbharat (11031) | Panvel to Alipur Duar Jn | Mon | 3 of 7 | 3 h 34 min | 4 h 44 min | 0% |
| 5 | SMVB MLDT Amrit Bharatexp (13433) | Smvt Bengaluru to Malda Town | Tue | 3 of 7 | 3 h 34 min | 5 h 03 min | 0% |
| 6 | Amrit Bharat Express (19022) | Brahmapur to Udhna Jn | Daily | 7 of 7 | 3 h 10 min | 7 h 56 min | 0% |
| 7 | Amrit Bharat Express (16598) | Alipur Duar Jn to Smvt Bengaluru | Mon | 3 of 7 | 2 h 25 min | 2 h 51 min | 0% |
| 8 | Amrit Bharat Express (19726) | Darbhanga Jn to Khatipura | Mon to Sat | 7 of 7 | 2 h 21 min | 5 h 34 min | 14% |
| 9 | Amrit Bharat Express (22588) | Banaras to Sealdah | Tue, Fri, Sun | 3 of 7 | 2 h 03 min | 4 h 57 min | 0% |
| 10 | Amrit Bharat Express (15568) | Anand Vihar Terminal to Bapudm Motihari | Wed, Sat | 4 of 7 | 1 h 29 min | 2 h 29 min | 0% |
| 11 | Amrit Bharat Express (15567) | Bapudm Motihari to Anand Vihar Terminal | Tue, Fri | 4 of 7 | 1 h 26 min | 3 h 54 min | 0% |
| 12 | Amrit Bharat Express (15558) | Anand Vihar Terminal to Darbhanga Jn | Tue, Fri | 3 of 7 | 1 h 22 min | 2 h 27 min | 33% |
| 13 | BNRS Amritbharat (22590) | Hadapsar to Banaras | Daily | 7 of 7 | 1 h 14 min | 2 h 15 min | 0% |
| 14 | Amrit Bharat Express (22362) | New Delhi to Rajendra Nagar Terminal | Daily | 6 of 7 | 0 h 57 min | 1 h 42 min | 0% |
| 15 | BAM Amrit Bharat (19021) | Udhna Jn to Brahmapur | Daily | 7 of 7 | 0 h 54 min | 2 h 45 min | 0% |
Thirteen of the 15 were never on time on any day we saw them. The exceptions are 15558, which was on time on one of its three days, and 19726, which was on time on one of its seven. 16602 also had one day cancelled in the window.
Where is your train right now?
Live position, expected arrival at every stop and the delay history of the last few weeks.
How to read these numbers
Several trains have only three or four days in the sample. With so few reports, one very late run can move the average a lot. That is why the worst-day column matters as much as the average.
Take 16602. Its average was 3 h 45 min, but its median largest delay was 47 minutes, so one very late day pulled the average up. Its worst day was 10 h 12 min.
Trains with seven days of reports give a steadier picture. 19022 averaged 3 h 10 min, with its worst day at 7 h 56 min. 19021 averaged 54 minutes across seven days, and 22590 averaged 1 h 14 min.
What to do before you travel
- Check the train's live status on the day you travel, not last week's average.
- Look at the worst day and the days seen before you decide. A high average from three days of data is a weaker signal than the same average over seven days.
- If the train is essential for a connection, leave a buffer. Do not plan a same-day connection on the tightest timing the timetable allows.
- Compare other options on the same route in the trip planner. A train that is late on average may still be a good choice on a day when it runs close to time.
Where this fits
For the same period across all train types, see the most delayed trains report for 29 October to 4 November 2026. Train 14663 appears in both reports. For an earlier look at the Amrit Bharat fleet, read our punctuality report for the week ending 5 October.
Use it on your trip
Frequently asked questions
Is this an official Indian Railways figure?
No. It comes from TrainLiveStatus's own delay tracking, built from running status reports. It is not an official statistic, and railway zones publish their own figures, which can differ from ours.
Why do several trains have only three days in the sample?
A train needs enough reports to be ranked, and several of these trains had reports on only three days. With so few days, one very late run can change the average a lot, so check the worst day and the days seen before you draw a conclusion.
Should I avoid these trains?
Not necessarily. The table shows how these trains ran in one week, not how they will run on your date. Check the live status on the day you travel and compare other options in the trip planner.
What counts as on time?
A train is on time on a day when the largest delay reported during that day's run is within 15 minutes. A train that was late for part of the run but caught up is still counted by its largest reported delay.
Sources
Rules and fares change. Check the official source before you travel. Last reviewed 5 November 2026.
