12239 Mumbai Central - Hisar Duronto Time Table
- Arrives
- 20:20 day 2
- Hisar HSR
- Journey
- 21h 10m
- 1504 km · 12 stops
12239 Mumbai Central - Hisar Duronto leaves Mumbai Central (MMCT) at 23:10 and reaches Hisar (HSR) at 20:20 on day 2 of the run. The booked run is 1504 km in 21h 10m, with 12 stops including both ends. It is the only train this timetable version books from Mumbai Central (MMCT) through to Hisar (HSR). Runs Tue, Sun.
12239 at a glance
| Runs on | Tue, Sun |
|---|---|
| Calendar row for this train | to — beyond 2026-09-30, so not a date we stand behind |
| Timetable version covers | to |
| Average speed | 71.1 km/h including halts — ours (how) |
| Type | Duronto · Premium |
| Reservation | Reserved (PRS) train. 12239 is a 1-, 2- or 8-series number: those are reserved. (how we decide) |
Time table and route
| Station | Arrives | Departs | Halt | Km |
|---|---|---|---|---|
| MMCT Mumbai Central | start | 23:10 | — | 0 |
| BRC Vadodara Jn | 03:26 +1 | 03:36 +1 | 10m | 392 |
| RTM Ratlam Jn | 07:00 +1 | 07:05 +1 | 5m | 649 |
| KOTA Kota Jn | 10:00 +1 | 10:05 +1 | 5m | 916 |
| SWM Sawai Madhopur Jn | 11:30 +1 | 11:50 +1 | 20m | 1023 |
| JP Jaipur Jn | 13:40 +1 | 13:50 +1 | 10m | 1155 |
| RGS Ringas Jn | 14:35 +1 | 14:38 +1 | 3m | 1212 |
| SIKR Sikar Jn | 15:35 +1 | 15:40 +1 | 5m | 1262 |
| JJN Jhunjhunu | 16:33 +1 | 16:35 +1 | 2m | 1327 |
| LHU Loharu | 17:35 +1 | 17:38 +1 | 3m | 1384 |
| SDLP Sadulpur Jn | 18:35 +1 | 19:00 +1 | 25m | 1434 |
| HSR Hisar | 20:20 +1 | end | — | 1504 |
What 12239’s schedule looks like
Its longest run without a stop is 392 km and 4h 16m from Mumbai Central (MMCT) to Vadodara Jn (BRC). The next longest is 267 km and 2h 55m from Ratlam Jn (RTM) to Kota Jn (KOTA).
At 06:00 on day 2 of the run it is between Vadodara Jn (BRC) and Ratlam Jn (RTM).
7 of its 10 intermediate stops are booked for five minutes or more, the longest of them 25 minutes at Sadulpur Jn (SDLP), 20 minutes at Sawai Madhopur Jn (SWM), 10 minutes at Vadodara Jn (BRC), 10 minutes at Jaipur Jn (JP), 5 minutes at Ratlam Jn (RTM). The briefest stop is 2 minutes at Jhunjhunu (JJN).
The run crosses midnight before Vadodara Jn (BRC); every later time carries a day marker.
It passes its own halfway mark of 752 km at Kota Jn (KOTA), stop number 4 of 12, and is booked to stand at its stops for 88 minutes in all, 7% of the 21h 10m journey.
Its quickest booked leg is Mumbai Central (MMCT) to Vadodara Jn (BRC), 392 km at an average of 92 km/h.
After Mumbai Central it calls first at Vadodara Jn (BRC), Ratlam Jn (RTM), Kota Jn (KOTA), Sawai Madhopur Jn (SWM) and Jaipur Jn (JP).
Its last stops before Hisar are Ringas Jn (RGS), Sikar Jn (SIKR), Jhunjhunu (JJN), Loharu (LHU) and Sadulpur Jn (SDLP).
Its stops are not evenly spread: 2 of the 10 fall in the first half of the distance and 8 in the second.
The busiest stations on its route are Vadodara Jn (BRC), where 454 trains call, Ratlam Jn (RTM), where 301 trains call, Jaipur Jn (JP), where 276 trains call.
At BRC it is booked in at 03:26 and away again at 03:36, 392 km into the run.
Other trains that share 12239’s route
From 12239’s halt rows, not its name. Trains without a page here are left out.
- 14724 Tirupati - Hisar Express — TPTY to HSR, 9 stations in common with 12239
- 14712 Bandra Terminus - Bikaner Jn Express — BDTS to BKN, 7 stations in common with 12239
- 12955 Mumbai Central Jaipur Superfast — MMCT to JP, 6 stations in common with 12239
- 12953 Mumbai Central - Hazrat Nizamuddin Jn AK Tejas Rajdhani Express — MMCT to NZM, 5 stations in common with 12239
Reservation chart and seat availability
12239 is booked out of Mumbai Central at 23:10, which puts it under rule RB-16.12.2025-B: its first reservation chart is expected at about 13:10 on the day of the journey. How we work this out.
It assumes 12239 is charted at Mumbai Central. 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 12239 — Mumbai Central to Hisar, 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 13:10 above comes from a published railway order, worked out, never observed.