Rajdhani Punctuality, 11 to 17 November 2026: Our Delay Data
Our own delay tracking for 11 to 17 November 2026 ranks 33 Rajdhani trains. See the 15 most delayed, the on-time shares and the method behind them.

In the seven days from 11 to 17 November 2026, our own delay tracking ranked 33 of the 52 Rajdhani trains in scope. Across the ranked trains, the average largest daily delay was 70 minutes, and 29% of runs finished within 15 minutes of schedule. The Dibrugarh to New Delhi Rajdhani Express (12423) had the highest average in this window, at 230 minutes.
How we measured it
This report uses only TrainLiveStatus's own delay tracking, covering seven days from 11 to 17 November 2026. For each train and each day, we take the largest delay reported during that day's run, in minutes. A run is on time when that largest delay is within 15 minutes. Averages are per train, taken over the days we observed that train, so a train seen on only three days is ranked on those three days.
This is our own tracking, not an official statistic. Rajdhani here follows the train type in our database, so Tejas Rajdhani services are counted under Rajdhani. The window ends on the publishing day, so today's figures may be only partly recorded.
The 15 most delayed Rajdhani trains
Trains are sorted by average largest delay, highest first. Only the 15 worst are shown, out of the 33 ranked.
| # | Train | Route | Days | Avg (min) | Median (min) | Worst day (min) | On time |
|---|---|---|---|---|---|---|---|
| 1 | 12423 Rajdhani Express | Dibrugarh to New Delhi | 7 | 230 | 244 | 430 | 0% |
| 2 | 22824 BBS Tejas Rajdhani | New Delhi to Bhubaneswar | 5 | 199 | 52 | 548 | 0% |
| 3 | 12302 HWH Rajdhani | New Delhi to Howrah Jn | 7 | 188 | 39 | 717 | 14% |
| 4 | 12314 Sealdah Rajdhni | New Delhi to Sealdah | 7 | 172 | 43 | 546 | 0% |
| 5 | 12310 RJPB Tejas Rajdhani | New Delhi to Rajendra Nagar Terminal | 7 | 160 | 123 | 392 | 0% |
| 6 | 12425 Jammu Rajdhani | New Delhi to Jammutavi | 7 | 159 | 170 | 255 | 0% |
| 7 | 20503 Rajdhani Express | Dibrugarh to New Delhi | 7 | 141 | 185 | 229 | 29% |
| 8 | 12424 Dbrt Rajdhani | New Delhi to Dibrugarh | 7 | 124 | 64 | 474 | 0% |
| 9 | 12309 RJPB Tejas Rajdhani | Rajendra Nagar Terminal to New Delhi | 7 | 115 | 21 | 405 | 43% |
| 10 | 12431 TVC NZM Rajdhani | Thiruvananthapuram Central to Hazrat Nizamuddin Jn | 5 | 79 | 82 | 117 | 20% |
| 11 | 22812 BBS Tejas Rajdhani | New Delhi to Bhubaneswar | 3 | 74 | 44 | 142 | 0% |
| 12 | 12301 Rajdhani Express | Howrah Jn to New Delhi | 7 | 70 | 35 | 318 | 29% |
| 13 | 12313 Rajdhani Express | Sealdah to New Delhi | 7 | 65 | 31 | 290 | 14% |
| 14 | 22691 Rajdhani Express | Ksr Bengaluru to Hazrat Nizamuddin Jn | 7 | 62 | 67 | 129 | 14% |
| 15 | 22823 Tejas Rajdhani Express | Bhubaneswar to New Delhi | 6 | 59 | 14 | 291 | 50% |
Where is your train right now?
Live position, expected arrival at every stop and the delay history of the last few weeks.
Average and median tell different stories
For several trains the average sits well above the median, which means a few very late days pulled the figure up. The HWH Rajdhani (12302) has a median of 39 minutes but an average of 188, and its worst day in the window was 717 minutes, the highest in the table. The Tejas Rajdhani Express from Bhubaneswar (22823) shows the same pattern, with a median of 14 minutes against an average of 59.
Read the two figures together. The average shows how bad the worst days were, and the median shows what a typical run looked like in this window.
The closest to time
Among the 15 shown, the best on-time shares belong to the Bhubaneswar to New Delhi Tejas Rajdhani Express (22823), within 15 minutes on 50% of its six observed days, and the RJPB Tejas Rajdhani from Rajendra Nagar Terminal (12309), within 15 minutes on 43% of its seven days. The Rajdhani Express from Dibrugarh (20503) and from Howrah (12301) were both on time on 29%.
Small samples to read with care
The BBS Tejas Rajdhani from New Delhi (22812) was observed on only three days, so its 74-minute average rests on very little data. The TVC NZM Rajdhani (12431) and the BBS Tejas Rajdhani from New Delhi (22824) were observed on five days each. Those rows should be read as a snapshot, not a settled pattern.
What to do with this
- Before you book, open the train's page and read its delay history rather than relying on one week's average. Start with the 12423 page if you are on that route.
- Compare the on-time share and the median with the average. A train with a low median can still have bad days, so plan a buffer for connections.
- On the day of travel, use live status and arrival alerts on the train's page, which show the current position rather than a weekly average.
- Keep this list in context: it is based on our tracked runs in one week, and it cannot tell you how your particular run will go.
For more on how to read punctuality data, see understanding a train's punctuality before booking and why apps show different delays for the same train. Earlier weeks are in Rajdhani punctuality, 27 October to 2 November and Rajdhani punctuality, 12 to 18 October.
Use it on your trip
Frequently asked questions
Which Rajdhani had the largest average delay this week?
In our tracking for 11 to 17 November 2026, the Dibrugarh to New Delhi Rajdhani Express (12423) had the highest average largest daily delay, at 230 minutes, and it was never within 15 minutes on the seven days we observed it. This is our own data, not an official statistic.
Did any Rajdhani run on time this week?
Some did, but on-time runs were rare. The Bhubaneswar to New Delhi Tejas Rajdhani Express (22823) was within 15 minutes on 50% of its six observed days, and the RJPB Tejas Rajdhani from Rajendra Nagar Terminal (12309) was on time on 43% of its seven days.
Does this mean Rajdhani trains are always late?
No. Across the 33 ranked trains, 29% of runs were within 15 minutes, which means most runs were not. But the figures come from one week of our own tracking, and several trains were observed on only three to six days, so treat them as a snapshot rather than a permanent pattern.
Should I change my booking because my Rajdhani is on this list?
Not on this report alone. An average over a week cannot tell you how your specific run will go. Check the train's page for its delay history, plan a buffer for any connection, and use live status and arrival alerts on the day of travel.
Sources
Rules and fares change. Check the official source before you travel. Last reviewed 17 November 2026.




