Vande Bharat Punctuality, 27 Oct to 2 Nov 2026: Our Delay Data
Our own delay tracking for Vande Bharat trains from 27 October to 2 November 2026: the 15 most delayed by average, with method notes and live status links.

From 27 October to 2 November 2026, our own delay tracking ranked 91 of the 118 Vande Bharat trains in scope. Across them, the average largest daily delay was 22 minutes, and 50% were on time (within 15 minutes). The most delayed on average was the Vande Bharat Express (20835) from Rourkela to Puri, at 94 minutes.

What we measured and how
This report uses only TrainLiveStatus's own delay tracking for seven days, 27 October to 2 November 2026. For each train we record the largest delay reported during that day's run, in minutes. On time means within 15 minutes. Averages are per train, taken over the days we observed that train.
This is our own tracking, not an official statistic. The window ends on the publishing day, so the last day may be only partly recorded.
The 15 most delayed Vande Bharat trains
Trains are sorted by average largest delay, highest first. The table also shows the median, which is less affected by a single very late day, and the worst day we recorded.
| # | Train | Route | Days observed | Avg largest delay (min) | Median (min) | Worst day (min) | On time |
|---|---|---|---|---|---|---|---|
| 1 | Vande Bharat Express (20835) | Rourkela to Puri | 5 | 94 | 94 | 111 | 0% |
| 2 | PUNE Vandebharat (26102) | Ajni to Pune Jn | 6 | 86 | 77 | 168 | 17% |
| 3 | Vande Bharat Express (22550) | Prayagraj Jn to Gorakhpur Jn | 6 | 84 | 88 | 137 | 0% |
| 4 | Vande Bharat Express (20891) | Tatanagar Jn to Brahmapur | 7 | 69 | 37 | 273 | 0% |
| 5 | Vande Bharat Express (20841) | Bhubaneswar to Visakhapatnam | 3 | 60 | 75 | 87 | 0% |
| 6 | Vande Bharat Express (22546) | Dehradoon to Lucknow | 6 | 46 | 40 | 65 | 0% |
| 7 | Vande Bharat Express (22346) | Gomti Nagar to Patna Jn | 5 | 41 | 15 | 102 | 60% |
| 8 | Vande Bharat Express (22348) | Patna Jn to Howrah Jn | 5 | 41 | 45 | 63 | 0% |
| 9 | Vande Bharat Express (20892) | Brahmapur to Tatanagar Jn | 5 | 41 | 38 | 64 | 0% |
| 10 | BSP Vande Bharat (20826) | Nagpur Jn to Bilaspur Jn | 4 | 39 | 35 | 58 | 0% |
| 11 | Vande Bharat Express (20834) | Secunderabad Jn to Visakhapatnam | 4 | 38 | 36 | 53 | 0% |
| 12 | Vande Bharat Express (22895) | Howrah Jn to Puri | 5 | 35 | 37 | 52 | 0% |
| 13 | Vande Bharat Express (22347) | Howrah Jn to Patna Jn | 5 | 34 | 30 | 60 | 20% |
| 14 | Vandebharat Express (20978) | Chandigarh to Ajmer Jn | 7 | 31 | 34 | 66 | 14% |
| 15 | SC Vande Bharat (20702) | Tirupati to Secunderabad Jn | 5 | 30 | 30 | 32 | 0% |
Eleven of the 15 were never within 15 minutes on any day we observed them. The four exceptions are the PUNE Vandebharat (26102) at 17%, the Vande Bharat Express (22346) from Gomti Nagar to Patna Junction at 60%, the Vande Bharat Express (22347) at 20%, and the Vandebharat Express (20978) at 14%.
The 20835 was observed on five days and averaged 94 minutes, with a median of the same figure and a worst day of 111 minutes. None of its observed runs were on time.
Where is your train right now?
Live position, expected arrival at every stop and the delay history of the last few weeks.
Where the most delayed trains run
Odisha stands out in this list. Five of the 15 start or end at Puri, Bhubaneswar or Brahmapur, including the Howrah Junction to Puri service (22895), the Bhubaneswar to Visakhapatnam service (20841), and the Tatanagar to Brahmapur service (20891) and its return train 20892.
The Patna and Howrah corridor also appears three times. The Patna Junction to Howrah (22348) and the Howrah to Patna Junction (22347) sit alongside the Gomti Nagar to Patna service (22346), which was on time most often of the three, at 60% of its observed days.
Averages versus medians
Some trains look worse on the average than on a typical day. The 20891 averaged 69 minutes but had a median of 37 minutes and a worst day of 273 minutes. A few very late days lift the average, so the median is the better guide to a usual run.
The reverse is also useful to know. The 20835 has an average and median close together, which means it was late by a similar amount on most days, not just on a few.
Two trains in the list, the 20841 and the 20834, each recorded one cancelled day in the window. Their averages come from fewer observed days, so treat them as a smaller sample.
What travellers should do
- Check the live status of your Vande Bharat on the day of travel, including the station board for your boarding station.
- If you have a tight onward connection, allow more buffer than the schedule suggests for any train on this list.
- Compare with other trains on your route in the trip planner before you change your plans.
For the earlier weekly report, see the Vande Bharat punctuality report for 12 to 18 October. For what sets the trains apart, read What Actually Makes Vande Bharat Different From Normal Trains.
Use it on your trip
Frequently asked questions
What period does this report cover?
Seven days, from 27 October to 2 November 2026. The window ends on the publishing day, so the last day may be only partly recorded in our tracking.
How many Vande Bharat trains were included?
118 Vande Bharat trains were in scope and 91 were ranked, with the 15 most delayed shown in the table above.
Why is the average so different from the median for some trains?
A few very late days raise the average without changing the typical day. The 20891 is an example, with a 69 minute average, a 37 minute median and a worst day of 273 minutes.
Should I change my booking if my Vande Bharat is in this list?
Not on this evidence alone. Check the live status of your train closer to the date and the official rules for your ticket. For a fixed-time commitment, plan a buffer.
Sources
Rules and fares change. Check the official source before you travel. Last reviewed 2 November 2026.



