20497 Rameswaram - Firozpur Cantt Superfast Humsafar Time Table
- Departs
- 22:50
- Rameswaram RMM
- Arrives
- 13:55 day 4
- Firozpur Cantt FZR
- Journey
- 63h 05m
- 3540 km · 43 stops
20497 Rameswaram - Firozpur Cantt Superfast Humsafar leaves Rameswaram (RMM) at 22:50 and reaches Firozpur Cantt (FZR) at 13:55 on day 4 of the run. The booked run is 3540 km in 63h 05m, with 43 stops including both ends. It is the only train this timetable version books from Rameswaram (RMM) through to Firozpur Cantt (FZR). Runs Tue.
20497 at a glance
| Runs on | Tue |
|---|---|
| Calendar row for this train | to — beyond 2026-09-30, so not a date we stand behind |
| Timetable version covers | to |
| Average speed | 56.1 km/h including halts — ours (how) |
| Type | Humsafar · Premium |
| Reservation | Reserved (PRS) train. 20497 is a 1-, 2- or 8-series number: those are reserved. (how we decide) |
Time table and route
| Station | Arrives | Departs | Halt | Km |
|---|---|---|---|---|
| RMM Rameswaram | start | 22:50 | — | 0 |
| RMD Ramanathapuram | 23:38 | 23:40 | 2m | 52 |
| MNM Manamadurai Jn | 00:18 +1 | 00:20 +1 | 2m | 111 |
| PDKT Pudukkottai | 01:43 +1 | 01:45 +1 | 2m | 215 |
| TPJ Tiruchchirappalli Jn | 03:00 +1 | 03:10 +1 | 10m | 267 |
| ALU Ariyalur | 04:05 +1 | 04:06 +1 | 1m | 337 |
| VM Villupuram Jn | 05:40 +1 | 05:45 +1 | 5m | 445 |
| CGL Chengalpattu Jn | 07:08 +1 | 07:10 +1 | 2m | 548 |
| MS Chennai Egmore | 08:25 +1 | 08:40 +1 | 15m | 603 |
| GDR Gudur Jn | 11:23 +1 | 11:25 +1 | 2m | 744 |
| NLR Nellore | 11:53 +1 | 11:55 +1 | 2m | 783 |
| BZA Vijayawada Jn | 15:40 +1 | 15:50 +1 | 10m | 1037 |
| WL Warangal | 18:58 +1 | 19:00 +1 | 2m | 1244 |
| BPQ Balharshah | 23:10 +1 | 23:15 +1 | 5m | 1490 |
| CD Chandrapur | 23:30 +1 | 23:32 +1 | 2m | 1504 |
| NGP Nagpur Jn | 02:20 +2 | 02:25 +2 | 5m | 1698 |
| BZU Betul | 04:50 +2 | 04:52 +2 | 2m | 1887 |
| ET Itarsi Jn | 07:45 +2 | 07:50 +2 | 5m | 1994 |
| BPL Bhopal Jn | 09:30 +2 | 09:40 +2 | 10m | 2086 |
| MKC Maksi Junction | 11:38 +2 | 11:40 +2 | 2m | 2228 |
| DWX Dewas | 12:13 +2 | 12:15 +2 | 2m | 2264 |
| LMNR Lakshmibai NGR | 13:15 +2 | 13:30 +2 | 15m | 2302 |
| FTD Fatehabad CH.Jn | 14:15 +2 | 14:17 +2 | 2m | 2338 |
| RTM Ratlam Jn | 15:45 +2 | 15:50 +2 | 5m | 2417 |
| MDS Mandasor | 16:56 +2 | 16:58 +2 | 2m | 2501 |
| NMH Nimach | 17:56 +2 | 17:58 +2 | 2m | 2550 |
| COR Chittaurgarh Jn | 19:25 +2 | 19:30 +2 | 5m | 2606 |
| BHL Bhilwara | 20:35 +2 | 20:40 +2 | 5m | 2660 |
| AII Ajmer Jn | 22:45 +2 | 22:55 +2 | 10m | 2792 |
| KSG Kishangarh | 23:22 +2 | 23:24 +2 | 2m | 2817 |
| JP Jaipur Jn | 01:15 +3 | 01:30 +3 | 15m | 2926 |
| RGS Ringas Jn | 02:20 +3 | 02:23 +3 | 3m | 2984 |
| SIKR Sikar Jn | 03:10 +3 | 03:15 +3 | 5m | 3034 |
| CUR Churu | 05:15 +3 | 05:35 +3 | 20m | 3124 |
| SDLP Sadulpur Jn | 06:20 +3 | 06:25 +3 | 5m | 3182 |
| TSD Tahsil Bhadra | 07:14 +3 | 07:16 +3 | 2m | 3246 |
| NHR Nohar | 07:48 +3 | 07:50 +3 | 2m | 3286 |
| ENB Ellenabad | 08:21 +3 | 08:23 +3 | 2m | 3317 |
| HMH Hanumangarh Jn | 09:25 +3 | 09:30 +3 | 5m | 3360 |
| SGRA Sangaria | 09:53 +3 | 09:55 +3 | 2m | 3387 |
| MBY Mandi Dabwali | 10:20 +3 | 10:23 +3 | 3m | 3417 |
| BTI Bathinda | 11:35 +3 | 11:45 +3 | 10m | 3452 |
| FZR Firozpur Cantt | 13:55 +3 | end | — | 3540 |
What 20497’s schedule looks like
Its longest run without a stop is 254 km and 3h 45m from Nellore (NLR) to Vijayawada Jn (BZA). The next longest is 246 km and 4h 10m from Warangal (WL) to Balharshah (BPQ).
At 22:00 on day 2 of the run it is between Warangal (WL) and Balharshah (BPQ), and at 06:00 on day 2 of the run it is between Villupuram Jn (VM) and Chengalpattu Jn (CGL).
19 of its 41 intermediate stops are booked for five minutes or more, the longest of them 20 minutes at Churu (CUR), 15 minutes at Chennai Egmore (MS), 15 minutes at Lakshmibai NGR (LMNR), 15 minutes at Jaipur Jn (JP), 10 minutes at Tiruchchirappalli Jn (TPJ). The briefest stop is 1 minute at Ariyalur (ALU).
The run crosses midnight before Manamadurai Jn (MNM); every later time carries a day marker.
It passes its own halfway mark of 1770 km at Betul (BZU), stop number 17 of 43, and is booked to stand at its stops for 210 minutes in all, 6% of the 63h 05m journey.
Its quickest booked leg is Ramanathapuram (RMD) to Manamadurai Jn (MNM), 59 km at an average of 93 km/h.
After Rameswaram it calls first at Ramanathapuram (RMD), Manamadurai Jn (MNM), Pudukkottai (PDKT), Tiruchchirappalli Jn (TPJ) and Ariyalur (ALU).
Its last stops before Firozpur Cantt are Ellenabad (ENB), Hanumangarh Jn (HMH), Sangaria (SGRA), Mandi Dabwali (MBY) and Bathinda (BTI).
Its stops are not evenly spread: 15 of the 41 fall in the first half of the distance and 26 in the second.
The busiest stations on its route are Chennai Egmore (MS), where 495 trains call, Vijayawada Jn (BZA), where 480 trains call, Itarsi Jn (ET), where 417 trains call.
At MS it is booked in at 08:25 and away again at 08:40, 603 km into the run.
Other trains that share 20497’s route
From 20497’s halt rows, not its name. Trains without a page here are left out.
- 22631 Madurai Jn - Bikaner Jn Anuvrat Superfast Express — MDU to BKN, 15 stations in common with 20497
- 22673 Jodhpur Jn - Mannargudi Superfast Express — JU to MQ, 13 stations in common with 20497
- 14724 Tirupati - Hisar Express — TPTY to HSR, 12 stations in common with 20497
- 12642 Hazrat Nizamuddin Jn - Kanniyakumari Tirukkural Express — NZM to CAPE, 11 stations in common with 20497
Reservation chart and seat availability
20497 is booked out of Rameswaram at 22:50, which puts it under rule RB-16.12.2025-B: its first reservation chart is expected at about 12:50 on the day of the journey. How we work this out.
It assumes 20497 is charted at Rameswaram. 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 20497 — Rameswaram to Firozpur Cantt, 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 12:50 above comes from a published railway order, worked out, never observed.