Train Chart Vacancy

12379 Sealdah - Amritsar Jalianwala B Express Time Table

Departs
13:10
Sealdah SDAH
Arrives
15:50 day 2
Amritsar ASR
Journey
26h 40m
1901 km · 17 stops
Chart expected
about 20:00
the day before travel — a target, not a guarantee (what this rests on)

12379 Sealdah - Amritsar Jalianwala B Express leaves Sealdah (SDAH) at 13:10 and reaches Amritsar (ASR) at 15:50 on day 2 of the run. The booked run is 1901 km in 26h 40m, with 17 stops including both ends. It is the only train this timetable version books from Sealdah (SDAH) through to Amritsar (ASR). Runs Fri. That is a stop every 119 km on average.

12379 at a glance

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

Time table and route

17 stops from Sealdah SDAH to Amritsar ASR, timed by version , km counted from SDAH. +1 is the next day.
StationArrivesDepartsHaltKm
SDAH Sealdah start 13:10 — 0
BWN Bardhaman 14:29 14:31 2m 107
DGR Durgapur 15:15 15:17 2m 171
ASN Asansol Jn 15:52 15:57 5m 213
KMME Kumardubi 16:16 16:17 1m 231
DHN Dhanbad Jn 17:10 17:15 5m 270
KQR Koderma 18:30 18:32 2m 393
GAYA Gaya Jn 19:55 20:00 5m 469
SSM Sasaram 21:05 21:07 2m 572
DDU PT.Deen Dayal Upadhyaya Jn 22:33 22:40 7m 673
GOY Govindpuri 03:05 +1 03:10 +1 5m 1024
DLI Delhi Jn 09:00 +1 09:15 +1 15m 1455
UMB Ambala Cantt Jn 11:50 +1 11:55 +1 5m 1652
LDH Ludhiana Jn 13:23 +1 13:33 +1 10m 1766
JUC Jalandhar City 14:30 +1 14:35 +1 5m 1822
BEAS Beas 15:06 +1 15:08 +1 2m 1859
ASR Amritsar 15:50 +1 end — 1901

What 12379’s schedule looks like

Its longest run without a stop is 431 km and 5h 50m from Govindpuri (GOY) to Delhi Jn (DLI). The next longest is 351 km and 4h 25m from PT.Deen Dayal Upadhyaya Jn (DDU) to Govindpuri (GOY).

At 22:00 it is between Sasaram (SSM) and PT.Deen Dayal Upadhyaya Jn (DDU), and at 06:00 on day 2 of the run it is between Govindpuri (GOY) and Delhi Jn (DLI).

9 of its 15 intermediate stops are booked for five minutes or more, the longest of them 15 minutes at Delhi Jn (DLI), 10 minutes at Ludhiana Jn (LDH), 7 minutes at PT.Deen Dayal Upadhyaya Jn (DDU), 5 minutes at Asansol Jn (ASN), 5 minutes at Dhanbad Jn (DHN). The briefest stop is 1 minute at Kumardubi (KMME).

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

It passes its own halfway mark of 950 km at Govindpuri (GOY), stop number 11 of 17, and is booked to stand at its stops for 73 minutes in all, 5% of the 26h 40m journey.

Its quickest booked leg is Dhanbad Jn (DHN) to Koderma (KQR), 123 km at an average of 98 km/h.

After Sealdah it calls first at Bardhaman (BWN), Durgapur (DGR), Asansol Jn (ASN), Kumardubi (KMME) and Dhanbad Jn (DHN).

Its last stops before Amritsar are Delhi Jn (DLI), Ambala Cantt Jn (UMB), Ludhiana Jn (LDH), Jalandhar City (JUC) and Beas (BEAS).

Its stops are not evenly spread: 9 of the 15 fall in the first half of the distance and 6 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, Bardhaman (BWN), where 349 trains call.

How these are counted.

Other trains that share 12379’s route

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

Reservation chart and seat availability

12379 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 12379 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 12379 — Sealdah to Amritsar, 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.