LiveArrived at destinationUpdated 3970s ago
12379 JALIANWALA B EX
SEALDAH (SDAH) → AMRITSAR JN (ASR)
+54 min late
Current position: Arrived at AMRITSAR(ASR) at 16:44 03-Oct (Delay: 00:54)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
All stations
LIVE- SDAHSEALDAHPF 12Actual 13:10 · On time
- BWNBARDHAMANActual 14:48 / 14:50 · +19 min
- DGRDURGAPURPF 3Actual 15:27 / 15:30 · +12 min
- ASNASANSOL JNPF 4Actual 16:09 / 16:14 · +17 min
- KMMEKUMARDUBIPF 1Actual 16:40 / 16:42 · +24 min
- DHNDHANBAD JNPF 3Actual 17:14 / 17:20 · +4 min
- KQRKODERMAPF 4Actual 19:21 / 19:24 · +51 min
- GAYAGAYA JNPF 1Actual 20:26 / 20:36 · +31 min
- SSMSASARAMPF 2Actual 21:59 / 22:02 · +54 min
- DDUPT.DEEN DAYAL UPADHYAYA JNPF 7Actual 23:11 / 23:20 · +38 min
- GOYGOVINDPURIPF 1Actual 03:33 / 03:41 · +28 min
- DLIDELHI JNPF 11Actual 09:20 / 09:38 · +20 min
- UMBAMBALA CANTTPF 7Actual 12:56 / 13:09 · +66 min
- LDHLUDHIANA JNPF 2Actual 14:27 / 14:40 · +64 min
- JUCJALANDHAR CITYPF 1Actual 15:28 / 15:33 · +58 min
- BEASBEASPF 1Actual 16:03 / 16:06 · +57 min
- ASRAMRITSARPF 4Sch 15:50 → Destination · Exp 16:44 · +54 min
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1SLRD2GEN3GEN4HA15A16A27M18M29M310B111B212B313B414S115S216S317S418S519S620GEN21GEN22LPR
Average delay history
UNIQUE| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| SDAH SEALDAH | — | On time |
| BWN BARDHAMAN | +19 min | +19 min |
| DGR DURGAPUR | +12 min | +13 min |
| ASN ASANSOL JN | +17 min | +17 min |
| KMME KUMARDUBI | +24 min | +25 min |
| DHN DHANBAD JN | +4 min | +5 min |
| KQR KODERMA | +51 min | +52 min |
| GAYA GAYA JN | +31 min | +36 min |
| SSM SASARAM | +54 min | +55 min |
| DDU PT.DEEN DAYAL UPADHYAYA JN | +38 min | +40 min |
| GOY GOVINDPURI | +28 min | — |
Based on the train's recent running history — no other public site shows this per train.
Journey info
Journey start date: 02-Oct-2026 · Boarding station: SDAH
Data source: National Train Enquiry System (CRIS). Times in IST.
More trains from SEALDAH
Popular trains
⚠️ Live feed isn't responding — this data may be outdated. Retrying automatically.