Train Chart Vacancy

22317 Sealdah - Jammutavi Humsafar Express Time Table

Departs
13:10
Sealdah SDAH
Arrives
23:25 day 2
Jammutavi JAT
Journey
34h 15m
1952 km · 13 stops
Chart expected
about 20:00
the day before travel — a target, not a guarantee (what this rests on)

22317 Sealdah - Jammutavi Humsafar Express leaves Sealdah (SDAH) at 13:10 and reaches Jammutavi (JAT) at 23:25 on day 2 of the run. The booked run is 1952 km in 34h 15m, with 13 stops including both ends. It is the only train this timetable version books from Sealdah (SDAH) through to Jammutavi (JAT). Runs Mon. That is a stop every 163 km on average.

22317 at a glance

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

Time table and route

13 stops from Sealdah SDAH to Jammutavi JAT, timed by version , km counted from SDAH. +1 is the next day.
StationArrivesDepartsHaltKm
SDAH Sealdah start 13:10 — 0
ASN Asansol Jn 15:55 15:57 2m 213
DHN Dhanbad Jn 17:10 17:15 5m 270
GAYA Gaya Jn 19:55 20:00 5m 469
DDU PT.Deen Dayal Upadhyaya Jn 22:45 22:50 5m 673
BSB Varanasi 00:10 +1 00:20 +1 10m 692
LKO Lucknow Jn 06:05 +1 06:15 +1 10m 975
BE Bareilly(NR) 09:42 +1 09:44 +1 2m 1210
MB Moradabad 11:14 +1 11:24 +1 10m 1300
SRE Saharanpur Jn 15:00 +1 15:10 +1 10m 1493
UMB Ambala Cantt Jn 16:25 +1 16:40 +1 15m 1574
LDH Ludhiana Jn 18:06 +1 18:14 +1 8m 1688
JAT Jammutavi 23:25 +1 end — 1952

What 22317’s schedule looks like

Its longest run without a stop is 283 km and 5h 45m from Varanasi (BSB) to Lucknow Jn (LKO). The next longest is 264 km and 5h 11m from Ludhiana Jn (LDH) to Jammutavi (JAT).

At 22:00 it is between Gaya Jn (GAYA) and PT.Deen Dayal Upadhyaya Jn (DDU), and at 06:00 on day 2 of the run it is between Varanasi (BSB) and Lucknow Jn (LKO).

9 of its 11 intermediate stops are booked for five minutes or more, the longest of them 15 minutes at Ambala Cantt Jn (UMB), 10 minutes at Varanasi (BSB), 10 minutes at Lucknow Jn (LKO), 10 minutes at Moradabad (MB), 10 minutes at Saharanpur Jn (SRE). The briefest stop is 2 minutes at Asansol Jn (ASN).

The run crosses midnight before Varanasi (BSB); every later time carries a day marker.

It passes its own halfway mark of 976 km at Bareilly(NR) (BE), stop number 8 of 13, and is booked to stand at its stops for 82 minutes in all, 4% of the 34h 15m journey.

Its quickest booked leg is Ambala Cantt Jn (UMB) to Ludhiana Jn (LDH), 114 km at an average of 80 km/h.

After Sealdah it calls first at Asansol Jn (ASN), Dhanbad Jn (DHN), Gaya Jn (GAYA), PT.Deen Dayal Upadhyaya Jn (DDU) and Varanasi (BSB).

Its last stops before Jammutavi are Bareilly(NR) (BE), Moradabad (MB), Saharanpur Jn (SRE), Ambala Cantt Jn (UMB) and Ludhiana Jn (LDH).

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

The busiest stations on its route are Sealdah (SDAH), where 732 trains call, PT.Deen Dayal Upadhyaya Jn (DDU), where 400 trains call, Lucknow Jn (LKO), where 305 trains call.

How these are counted.

Other trains that share 22317’s route

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

Reservation chart and seat availability

22317 is booked out of Sealdah at 13:10, 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 22317 is charted at Sealdah. 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 22317 — Sealdah to Jammutavi, 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.