15614
LACHIT EXPRE
MZS → KYQ · Mail/Express · Running days not published
Current location
GOHPUR
Departed at 23:41
On time
Current speed
61 km/h
Delay
On time
(3 min)
Next stop
HELEM
Arriving at 00:02
Route & Live Status
All stations, with actual / expected times and platform numbers.
| # | Station | Sch. Arr | Sch. Dep | Actual / Exp | Delay | Platform | Status |
|---|---|---|---|---|---|---|---|
| 1 | -- | 19:00 | 19:00 | On time | -- | Departed | |
| 2 | 19:25 | 19:27 | 19:26 | +1 min | -- | Departed | |
| 3 | 19:41 | 19:43 | 19:42 | +1 min | -- | Departed | |
| 4 | 20:07 | 20:12 | 20:08 | +1 min | -- | Departed | |
| 5 | 20:40 | 20:42 | 20:42 | +2 min | -- | Departed | |
| 6 | 20:57 | 20:58 | 20:59 | +2 min | -- | Departed | |
| 7 | 21:08 | 21:10 | 21:10 | +2 min | -- | Departed | |
| 8 | 22:10 | 22:15 | 22:13 | +3 min | -- | Departed | |
| 9 | 22:33 | 22:35 | 22:36 | +3 min | -- | Departed | |
| 10 | 22:50 | 22:52 | 22:53 | +3 min | -- | Departed | |
| 11 | 23:10 | 23:12 | 23:13 | +3 min | -- | Departed | |
| 12 | 23:36 | 23:38 | 23:39 | +3 min | -- | Departed | |
| 13 | 23:59 | 00:01 | 00:02 | +3 min | -- | Upcoming | |
| 14 | 00:33 | 00:35 | 00:36 | +3 min | -- | Upcoming | |
| 15 | 01:35 | 01:37 | 01:38 | +3 min | -- | Upcoming | |
| 16 | 02:10 | 02:20 | 02:13 | +3 min | -- | Upcoming | |
| 17 | 02:37 | 02:39 | 02:40 | +3 min | -- | Upcoming | |
| 18 | 03:11 | 03:12 | 03:15 | +4 min | -- | Upcoming | |
| 19 | 03:23 | 03:24 | 03:27 | +4 min | -- | Upcoming | |
| 20 | 03:38 | 03:40 | 03:43 | +5 min | -- | Upcoming | |
| 21 | 04:01 | 04:03 | 04:07 | +6 min | -- | Upcoming | |
| 22 | 04:15 | 04:16 | 04:21 | +6 min | -- | Upcoming | |
| 23 | 04:28 | 04:29 | 04:35 | +7 min | -- | Upcoming | |
| 24 | 05:20 | 05:45 | 05:29 | +9 min | -- | Upcoming | |
| 25 | 07:05 | -- | 07:20 | +15 min | -- | Upcoming |
Every screen here runs on TrainLive's own reference timetable and a running simulation. Station names, codes and coordinates are real, but positions, delays, seat availability and PNR records are generated, not live railway data. Where our data comes from →