16601 Erode Jn - Jogbani Amrit Bharat Time Table
- Arrives
- 19:00 day 3
- Jogbani JBN
- Journey
- 58h 45m
- 3124 km · 51 stops
16601 Erode Jn - Jogbani Amrit Bharat leaves Erode Jn (ED) at 08:15 and reaches Jogbani (JBN) at 19:00 on day 3 of the run. The booked run is 3124 km in 58h 45m, with 51 stops including both ends. It is the only train this timetable version books from Erode Jn (ED) through to Jogbani (JBN). Runs Thu.
16601 at a glance
| Runs on | Thu |
|---|---|
| Calendar row for this train | to — beyond 2026-09-30, so not a date we stand behind |
| Timetable version covers | to |
| Average speed | 53.2 km/h including halts — ours (how) |
| Type | Amrit Bharat · Premium |
| Reservation | Reserved (PRS) train. 16601 is a 1-, 2- or 8-series number: those are reserved. (how we decide) |
Time table and route
| Station | Arrives | Departs | Halt | Km |
|---|---|---|---|---|
| ED Erode Jn | start | 08:15 | — | 0 |
| SA Salem Jn | 09:00 | 09:05 | 5m | 59 |
| JTJ Jolarpettai Jn | 10:48 | 10:50 | 2m | 183 |
| KPD Katpadi Jn | 12:00 | 12:10 | 10m | 267 |
| AJJ Arakkonam Jn | 12:58 | 13:00 | 2m | 328 |
| PER Perambur | 13:45 | 13:50 | 5m | 391 |
| NYP Nayudupeta | 15:58 | 16:00 | 2m | 500 |
| GDR Gudur Jn | 16:40 | 16:50 | 10m | 528 |
| OGL Ongole | 18:58 | 19:00 | 2m | 682 |
| BZA Vijayawada Jn | 21:15 | 21:25 | 10m | 820 |
| KMT Khammam | 00:04 +1 | 00:05 +1 | 1m | 921 |
| WL Warangal | 01:38 +1 | 01:40 +1 | 2m | 1027 |
| MCI Mancheral | 03:34 +1 | 03:35 +1 | 1m | 1144 |
| BPQ Balharshah | 06:10 +1 | 06:15 +1 | 5m | 1273 |
| CD Chandrapur | 06:30 +1 | 06:32 +1 | 2m | 1287 |
| SEGM Sevagram | 08:13 +1 | 08:15 +1 | 2m | 1405 |
| NGP Nagpur Jn | 09:55 +1 | 10:00 +1 | 5m | 1481 |
| BZU Betul | 12:38 +1 | 12:40 +1 | 2m | 1670 |
| GDYA Ghoradongri | 13:15 +1 | 13:17 +1 | 2m | 1707 |
| ET Itarsi Jn | 15:00 +1 | 15:10 +1 | 10m | 1777 |
| PPI Pipariya | 15:52 +1 | 15:54 +1 | 2m | 1844 |
| GAR Gadarwara | 16:16 +1 | 16:18 +1 | 2m | 1894 |
| JBP Jabalpur | 18:15 +1 | 18:25 +1 | 10m | 2022 |
| KTE Katni | 19:55 +1 | 20:00 +1 | 5m | 2113 |
| MYR Maihar | 20:43 +1 | 20:45 +1 | 2m | 2176 |
| STA Satna | 21:45 +1 | 21:50 +1 | 5m | 2211 |
| MKP Manikpur Jn | 23:35 +1 | 23:37 +1 | 2m | 2289 |
| DBR Dabhaura | 23:55 +1 | 23:57 +1 | 2m | 2311 |
| JSR Jasra | 00:53 +2 | 00:55 +2 | 2m | 2366 |
| PCOI Prayagraj Chheoki | 01:30 +2 | 01:35 +2 | 5m | 2381 |
| BDL Vindhyachal | 02:28 +2 | 02:30 +2 | 2m | 2454 |
| CAR Chunar | 03:05 +2 | 03:07 +2 | 2m | 2492 |
| DDU PT.Deen Dayal Upadhyaya Jn | 05:38 +2 | 05:45 +2 | 7m | 2525 |
| BXR Buxar | 06:51 +2 | 06:53 +2 | 2m | 2614 |
| RPR Raghunathpur | 07:18 +2 | 07:20 +2 | 2m | 2647 |
| ARA Ara | 07:55 +2 | 07:57 +2 | 2m | 2683 |
| DNR Danapur | 08:43 +2 | 08:45 +2 | 2m | 2722 |
| PPTA Patliputra | 09:25 +2 | 09:35 +2 | 10m | 2728 |
| SEE Sonpur | 10:11 +2 | 10:13 +2 | 2m | 2744 |
| HJP Hajipur Jn | 10:25 +2 | 10:30 +2 | 5m | 2749 |
| SPP Shahpur Patoree | 11:06 +2 | 11:08 +2 | 2m | 2787 |
| BJU Barauni Jn | 12:05 +2 | 12:15 +2 | 10m | 2837 |
| BGS Begusarai | 12:31 +2 | 12:33 +2 | 2m | 2852 |
| KGG Khagaria Jn | 13:18 +2 | 13:20 +2 | 2m | 2893 |
| MNE Mansi Jn | 13:28 +2 | 13:30 +2 | 2m | 2901 |
| NNA Naugachia | 14:26 +2 | 14:28 +2 | 2m | 2960 |
| KIR Katihar Jn | 16:05 +2 | 16:15 +2 | 10m | 3016 |
| PRNA Purnia Jn | 16:40 +2 | 16:42 +2 | 2m | 3044 |
| ARQ Arariya Court Jn | 17:13 +2 | 17:15 +2 | 2m | 3082 |
| FBG Forbesganj Jn | 17:50 +2 | 17:52 +2 | 2m | 3111 |
| JBN Jogbani | 19:00 +2 | end | — | 3124 |
What 16601’s schedule looks like
Its longest run without a stop is 189 km and 2h 38m from Nagpur Jn (NGP) to Betul (BZU). The next longest is 154 km and 2h 08m from Gudur Jn (GDR) to Ongole (OGL).
At 22:00 it is between Vijayawada Jn (BZA) and Khammam (KMT), and at 06:00 on day 2 of the run it is between Mancheral (MCI) and Balharshah (BPQ).
17 of its 49 intermediate stops are booked for five minutes or more, the longest of them 10 minutes at Katpadi Jn (KPD), 10 minutes at Gudur Jn (GDR), 10 minutes at Vijayawada Jn (BZA), 10 minutes at Itarsi Jn (ET), 10 minutes at Jabalpur (JBP). The briefest stop is 1 minute at Khammam (KMT).
The run crosses midnight before Khammam (KMT); every later time carries a day marker.
It passes its own halfway mark of 1562 km at Betul (BZU), stop number 18 of 51, and is booked to stand at its stops for 189 minutes in all, 5% of the 58h 45m journey.
Its quickest booked leg is Pipariya (PPI) to Gadarwara (GAR), 50 km at an average of 136 km/h.
After Erode Jn it calls first at Salem Jn (SA), Jolarpettai Jn (JTJ), Katpadi Jn (KPD), Arakkonam Jn (AJJ) and Perambur (PER).
Its last stops before Jogbani are Naugachia (NNA), Katihar Jn (KIR), Purnia Jn (PRNA), Arariya Court Jn (ARQ) and Forbesganj Jn (FBG).
Its stops are not evenly spread: 16 of the 49 fall in the first half of the distance and 33 in the second.
The busiest stations on its route are Vijayawada Jn (BZA), where 480 trains call, Itarsi Jn (ET), where 417 trains call, PT.Deen Dayal Upadhyaya Jn (DDU), where 400 trains call.
At BZA it is booked in at 21:15 and away again at 21:25, 820 km into the run.
Other trains that share 16601’s route
From 16601’s halt rows, not its name. Trains without a page here are left out.
- 22351 Saharsa Jn - SMVT Bengaluru Express — SHC to SMVB, 28 stations in common with 16601
- 12295 SMVT Bengaluru - Danapur Sanghamitra Express — SMVB to DNR, 26 stations in common with 16601
- 12577 Darbhanga Jn - Mysore Jn Bagmati Express — DBG to MYS, 25 stations in common with 16601
- 22670 Patna Jn - Ernakulam Jn Express — PNBE to ERS, 23 stations in common with 16601
Reservation chart and seat availability
16601 is booked out of Erode Jn at 08:15, which puts it under rule RB-16.12.2025-A: its first reservation chart is expected at about 20:00 on the day before the journey. How we work this out.
It assumes 16601 is charted at Erode Jn. The rule is press-reported: no circular number has been located, and the first report covered one zone. Preparation can be later. The circulars, the second chart and what is still unsettled.
Check live seat availability for 16601 — Erode Jn to Jogbani, fetched when you ask and never stored here (how).
Where this came from
Every time and distance above is read from timetable version , and from nothing else. Where the timetable data comes from.
The 20:00 above comes from a published railway order, worked out, never observed.