LiveArrived at destinationUpdated 0s ago
54559 BATHINDA FAZILKA VIA ABOHAR PASSENGER
BHATINDA JN (BTI) → FAZILKA JN (FKA)
On time
Current position: Arrived at FAZILKA(FKA) at 12:34 02-Oct (On Time)
Auto-refreshes every 45s · data: NTES
Share on WhatsApp
Next stations
BWX09:49 02-Oct
FSR10:19 02-Oct
BFE10:52 02-Oct
BJMA11:39 02-Oct
GHLU12:00 02-Oct
All stations
LIVE- BTIBATHINDAPF 3Actual 09:41 · +1 min
- BWXBAHMAN DIWANASch 09:49 → 09:50 · Exp **UA** / **UA** · On time
- BHXBULLUANAPF 1Sch 09:57 → 09:58 · Exp 10:02 / **UA** · +5 min
- GDBGIDDARBAHAPF 1Sch 10:08 → 10:10 · Exp 10:15 / 10:16 · +7 min
- FSRFAQARSARSch 10:19 → 10:20 · Exp **UA** / **UA** · +4 min
- MOTMALOUTPF 1Sch 10:28 → 10:30 · Exp 10:34 / 10:36 · +6 min
- PKKPAKKIPF 1Sch 10:43 → 10:44 · Exp 10:49 / 10:49 · +6 min
- BFEBAHAWAL BASISch 10:52 → 10:53 · Exp **UA** / **UA** · +6 min
- ABSABOHARPF 1Sch 11:10 → 11:30 · Exp 11:04 / 11:30 · On time
- BJMABURJ MOHARSch 11:39 → 11:40 · Exp **UA** / **UA** · On time
- CWDACWDAPF 1Sch 11:49 → 11:51 · Exp 11:55 / 11:56 · +6 min
- GHLUGHALLUSch 12:00 → 12:01 · Exp **UA** / **UA** · +5 min
- KUKAKUKAPF 1Sch 12:08 → 12:10 · Exp 12:11 / 12:13 · +3 min
- JWKAJANDWALA KHARTASch 12:21 → 12:22 · Exp **UA** / **UA** · +4 min
- FKAFAZILKAPF 1Sch 12:40 → Destination · Exp 12:34 · On time
Coach position
Numbered from the engine · → direction of travel🚂ENGINE→1SLRD2GEN3GEN4GEN5GEN6GEN7GEN8GEN9GEN10SLRD
Average delay history
UNIQUE| Station | Avg arr delay | Avg dep delay |
|---|---|---|
| BTI BATHINDA | — | +3 min |
| BHX BULLUANA | +10 min | +10 min |
| GDB GIDDARBAHA | +11 min | +11 min |
| MOT MALOUT | +9 min | +8 min |
| PKK PAKKI | +8 min | +8 min |
| ABS ABOHAR | On time | On time |
| CWDA CWDA | +7 min | +6 min |
| KUKA KUKA | +6 min | +6 min |
| FKA FAZILKA | On time | — |
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: BTI
Data source: National Train Enquiry System (CRIS). Times in IST.
Popular trains
⚠️ Live feed isn't responding — this data may be outdated. Retrying automatically.