Train Chart Vacancy

12449 Madgaon Junction - Chandigarh GOA Sampark Kranti Time Table

Departs
10:00
Madgaon Junction MAO
Arrives
18:25 day 2
Chandigarh CDG
Journey
32h 25m
2158 km · 16 stops
Chart expected
about 20:00
the day before travel — a target, not a guarantee (what this rests on)

12449 Madgaon Junction - Chandigarh GOA Sampark Kranti leaves Madgaon Junction (MAO) at 10:00 and reaches Chandigarh (CDG) at 18:25 on day 2 of the run. The booked run is 2158 km in 32h 25m, with 16 stops including both ends. It is the only train this timetable version books from Madgaon Junction (MAO) through to Chandigarh (CDG). Runs Tue, Wed.

12449 at a glance

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

Time table and route

16 stops from Madgaon Junction MAO to Chandigarh CDG, timed by version , km counted from MAO. +1 is the next day.
StationArrivesDepartsHaltKm
MAO Madgaon Junction start 10:00 — 0
KRMI Karmali 10:30 10:32 2m 29
THVM Thivim 10:50 10:52 2m 46
PERN Pernem 11:03 11:05 2m 57
RN Ratnagiri 14:45 14:50 5m 239
PNVL Panvel 19:37 19:40 3m 519
BSR Vasai Road 21:00 21:05 5m 583
ST Surat 23:48 23:53 5m 799
BRC Vadodara Jn 01:20 +1 01:30 +1 10m 928
RTM Ratlam Jn 05:00 +1 05:05 +1 5m 1185
KOTA Kota Jn 08:10 +1 08:20 +1 10m 1450
NZM Hazrat Nizamuddin Jn 13:41 +1 13:43 +1 2m 1908
NDLS New Delhi 14:10 +1 14:25 +1 15m 1915
PNP Panipat Jn 15:27 +1 15:29 +1 2m 2004
UMB Ambala Cantt Jn 17:40 +1 17:45 +1 5m 2113
CDG Chandigarh 18:25 +1 end — 2158

What 12449’s schedule looks like

Its longest run without a stop is 458 km and 5h 21m from Kota Jn (KOTA) to Hazrat Nizamuddin Jn (NZM). The next longest is 280 km and 4h 47m from Ratnagiri (RN) to Panvel (PNVL).

At 22:00 it is between Vasai Road (BSR) and Surat (ST), and at 06:00 on day 2 of the run it is between Ratlam Jn (RTM) and Kota Jn (KOTA).

8 of its 14 intermediate stops are booked for five minutes or more, the longest of them 15 minutes at New Delhi (NDLS), 10 minutes at Vadodara Jn (BRC), 10 minutes at Kota Jn (KOTA), 5 minutes at Ratnagiri (RN), 5 minutes at Vasai Road (BSR). The briefest stop is 2 minutes at Karmali (KRMI).

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

It passes its own halfway mark of 1079 km at Ratlam Jn (RTM), stop number 10 of 16, and is booked to stand at its stops for 73 minutes in all, 4% of the 32h 25m journey.

Its quickest booked leg is Surat (ST) to Vadodara Jn (BRC), 129 km at an average of 89 km/h.

After Madgaon Junction it calls first at Karmali (KRMI), Thivim (THVM), Pernem (PERN), Ratnagiri (RN) and Panvel (PNVL).

Its last stops before Chandigarh are Kota Jn (KOTA), Hazrat Nizamuddin Jn (NZM), New Delhi (NDLS), Panipat Jn (PNP) and Ambala Cantt Jn (UMB).

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

The busiest stations on its route are Vadodara Jn (BRC), where 454 trains call, Surat (ST), where 429 trains call, New Delhi (NDLS), where 335 trains call.

At BRC it is booked in at 01:20 and away again at 01:30, 928 km into the run.

How these are counted.

Other trains that share 12449’s route

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

Reservation chart and seat availability

12449 is booked out of Madgaon Junction at 10:00, 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.

A target, not a guarantee

It assumes 12449 is charted at Madgaon Junction. 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 12449 — Madgaon Junction to Chandigarh, 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.