Train Chart Vacancy

12953 Mumbai Central - Hazrat Nizamuddin Jn AK Tejas Rajdhani Express Time Table

Departs
17:10
Mumbai Central MMCT
Arrives
09:43 day 2
Hazrat Nizamuddin Jn NZM
Journey
16h 33m
1373 km · 13 stops
Chart expected
about 07:10
on the day of travel — a target, not a guarantee (what this rests on)

12953 Mumbai Central - Hazrat Nizamuddin Jn AK Tejas Rajdhani Express leaves Mumbai Central (MMCT) at 17:10 and reaches Hazrat Nizamuddin Jn (NZM) at 09:43 on day 2 of the run. The booked run is 1373 km in 16h 33m, with 13 stops including both ends. It is the quicker of the 2 trains booked from Mumbai Central (MMCT) to Hazrat Nizamuddin Jn (NZM), at 16h 33m.

12953 at a glance

12953 in timetable version .
Runs onDaily
Calendar row for this train to — beyond 2026-09-30, so not a date we stand behind
Timetable version covers to
Average speed83.0 km/h including halts — ours (how)
TypeTejas · Premium
ReservationReserved (PRS) train. 12953 is a 1-, 2- or 8-series number: those are reserved. (how we decide)

Time table and route

13 stops from Mumbai Central MMCT to Hazrat Nizamuddin Jn NZM, timed by version , km counted from MMCT. +1 is the next day.
StationArrivesDepartsHaltKm
MMCT Mumbai Central start 17:10 — 0
BVI Borivali 17:38 17:40 2m 30
VAPI Vapi 18:53 18:55 2m 168
BL Valsad 19:13 19:15 2m 194
ST Surat 20:10 20:15 5m 262
BH Bharuch Jn 20:53 20:55 2m 321
BRC Vadodara Jn 21:44 21:54 10m 392
DHD Dahod 23:38 23:40 2m 536
RTM Ratlam Jn 01:13 +1 01:15 +1 2m 649
KOTA Kota Jn 04:05 +1 04:15 +1 10m 916
SWM Sawai Madhopur Jn 05:23 +1 05:25 +1 2m 1023
MTJ Mathura Jn 07:53 +1 07:55 +1 2m 1240
NZM Hazrat Nizamuddin Jn 09:43 +1 end — 1373

What 12953’s schedule looks like

Of the 2 trains booked from Mumbai Central (MMCT) to Hazrat Nizamuddin Jn (NZM), the other is 22209 Mumbai Central - Hazrat Nizamuddin Jn Duronto at 16h 40m.

Its longest run without a stop is 267 km and 2h 50m from Ratlam Jn (RTM) to Kota Jn (KOTA). The next longest is 217 km and 2h 28m from Sawai Madhopur Jn (SWM) to Mathura Jn (MTJ).

At 22:00 it is between Vadodara Jn (BRC) and Dahod (DHD), and at 06:00 on day 2 of the run it is between Sawai Madhopur Jn (SWM) and Mathura Jn (MTJ).

3 of its 11 intermediate stops are booked for five minutes or more, the longest of them 10 minutes at Vadodara Jn (BRC), 10 minutes at Kota Jn (KOTA), 5 minutes at Surat (ST). The briefest stop is 2 minutes at Borivali (BVI).

The run crosses midnight before Ratlam Jn (RTM); every later time carries a day marker.

It passes its own halfway mark of 686 km at Kota Jn (KOTA), stop number 10 of 13, and is booked to stand at its stops for 41 minutes in all, 4% of the 16h 33m journey.

Its quickest booked leg is Borivali (BVI) to Vapi (VAPI), 138 km at an average of 113 km/h.

After Mumbai Central it calls first at Borivali (BVI), Vapi (VAPI), Valsad (BL), Surat (ST) and Bharuch Jn (BH).

Its last stops before Hazrat Nizamuddin Jn are Dahod (DHD), Ratlam Jn (RTM), Kota Jn (KOTA), Sawai Madhopur Jn (SWM) and Mathura Jn (MTJ).

Its stops are not evenly spread: 8 of the 11 fall in the first half of the distance and 3 in the second.

The busiest stations on its route are Vadodara Jn (BRC), where 454 trains call, Surat (ST), where 429 trains call, Ratlam Jn (RTM), where 301 trains call.

At BRC it is booked in at 21:44 and away again at 21:54, 392 km into the run.

How these are counted.

Other trains that share 12953’s route

From 12953’s halt rows, not its name. Trains without a page here are left out.

Reservation chart and seat availability

12953 is booked out of Mumbai Central at 17:10, which puts it under rule RB-16.12.2025-B: its first reservation chart is expected at about 07:10 on the day of the journey. How we work this out.

A target, not a guarantee

It assumes 12953 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 12953 — Mumbai Central to Hazrat Nizamuddin Jn, 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 07:10 above comes from a published railway order, worked out, never observed.