Train Chart Vacancy

22403 Pondicherry - New Delhi Superfast Express Time Table

Departs
09:55
Pondicherry PDY
Arrives
00:20 day 3
New Delhi NDLS
Journey
38h 25m
2379 km · 15 stops
Chart expected
about 20:00
the day before travel — a target, not a guarantee (what this rests on)

22403 Pondicherry - New Delhi Superfast Express leaves Pondicherry (PDY) at 09:55 and reaches New Delhi (NDLS) at 00:20 on day 3 of the run. The booked run is 2379 km in 38h 25m, with 15 stops including both ends. It is the only train this timetable version books from Pondicherry (PDY) through to New Delhi (NDLS). Runs Wed.

22403 at a glance

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

Time table and route

15 stops from Pondicherry PDY to New Delhi NDLS, timed by version , km counted from PDY. +1 is the next day, +2 the one after.
StationArrivesDepartsHaltKm
PDY Pondicherry start 09:55 — 0
VM Villupuram Jn 10:30 10:35 5m 38
MS Chennai Egmore 13:00 13:15 15m 196
GDR Gudur Jn 15:33 15:35 2m 337
BZA Vijayawada Jn 20:00 20:10 10m 630
WL Warangal 23:08 23:10 2m 836
SKZR Sirpur Kaghaznagar 02:09 +1 02:10 +1 1m 1012
BPQ Balharshah 03:20 +1 03:25 +1 5m 1082
NGP Nagpur Jn 06:45 +1 06:50 +1 5m 1291
ET Itarsi Jn 12:15 +1 12:20 +1 5m 1586
BPL Bhopal Jn 13:50 +1 13:55 +1 5m 1678
VGLJ Virangana Lakshmibai Jhansi Jn 18:00 +1 18:05 +1 5m 1968
AGC Agra Cantt Jn 21:05 +1 21:10 +1 5m 2185
MTJ Mathura Jn 21:45 +1 21:47 +1 2m 2238
NDLS New Delhi 00:20 +2 end — 2379

What 22403’s schedule looks like

Its longest run without a stop is 295 km and 5h 25m from Nagpur Jn (NGP) to Itarsi Jn (ET). The next longest is 293 km and 4h 25m from Gudur Jn (GDR) to Vijayawada Jn (BZA).

At 22:00 it is between Vijayawada Jn (BZA) and Warangal (WL), and at 06:00 on day 2 of the run it is between Balharshah (BPQ) and Nagpur Jn (NGP).

9 of its 13 intermediate stops are booked for five minutes or more, the longest of them 15 minutes at Chennai Egmore (MS), 10 minutes at Vijayawada Jn (BZA), 5 minutes at Villupuram Jn (VM), 5 minutes at Balharshah (BPQ), 5 minutes at Nagpur Jn (NGP). The briefest stop is 1 minute at Sirpur Kaghaznagar (SKZR).

The run crosses midnight before Sirpur Kaghaznagar (SKZR); every later time carries a day marker.

It passes its own halfway mark of 1190 km at Nagpur Jn (NGP), stop number 9 of 15, and is booked to stand at its stops for 67 minutes in all, 3% of the 38h 25m journey.

Its quickest booked leg is Agra Cantt Jn (AGC) to Mathura Jn (MTJ), 53 km at an average of 91 km/h.

After Pondicherry it calls first at Villupuram Jn (VM), Chennai Egmore (MS), Gudur Jn (GDR), Vijayawada Jn (BZA) and Warangal (WL).

Its last stops before New Delhi are Itarsi Jn (ET), Bhopal Jn (BPL), Virangana Lakshmibai Jhansi Jn (VGLJ), Agra Cantt Jn (AGC) and Mathura Jn (MTJ).

Its stops are not evenly spread: 7 of the 13 fall in the first half of the distance and 6 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 13:00 and away again at 13:15, 196 km into the run.

How these are counted.

Other trains that share 22403’s route

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

Reservation chart and seat availability

22403 is booked out of Pondicherry at 09:55, 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 22403 is charted at Pondicherry. 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 22403 — Pondicherry to New Delhi, 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.