Mehr Express 127UP — the run of 23 August 2026
The recorded journey of the run that departed Sunday 23 August 2026.
RouteMultan Cantt → Rawalpindi
First recordedSher Shah Jn, 16:57+25 min — names where it was first seen, not necessarily its origin
At Rawalpindithe record stops before Rawalpindi — last recorded at Fateh Jang
The record stops before Rawalpindi — last recorded at Fateh Jang at 07:16.
Every recorded crossing
this run onlyShow the 32 earlier stops
- Multan CanttNo recordArrive—Depart16:15Delay—
- Sher Shah JnCrossedArrive16:3216:57Depart16:3417:01Delay+25 min
- MuzaffargarhCrossedArrive16:5017:25Depart16:5217:29Delay+35 min
- BudhCrossedArrive17:0917:46Depart17:1017:48Delay+37 min
- Mehmood KotCrossedArrive17:2418:02Depart17:2618:06Delay+39 min
- GurmaniCrossedArrive17:3618:17Depart17:3718:19Delay+42 min
- SanawanCrossedArrive17:5118:30Depart17:5318:32Delay+40 min
- Kot AdduCrossedArrive18:1518:48Depart18:2519:02Delay+34 min
- Dera DinpanahCrossedArrive18:3619:14Depart18:3819:16Delay+38 min
- Ahsan Pur AhpCrossedArrive18:4919:26Depart18:5119:28Delay+37 min
- Kot SultanCrossedArrive19:0719:40Depart19:0919:44Delay+33 min
- Jaman ShahCrossedArrive19:2219:56Depart19:2420:03Delay+34 min
- LayyahCrossedArrive19:3520:15Depart19:4020:21Delay+40 min
- Karor Lal EsanCrossedArrive20:0620:55Depart20:0820:58Delay+50 min
- BehalCrossedArrive20:2821:27Depart20:3021:31Delay+59 min
- BhakkarCrossedArrive21:0022:06Depart21:0522:13Delay+1h 07m
- Darya KhanNo recordArrive21:34Depart21:36Delay—
- Kalur KotCrossedArrive22:5723:56Depart22:5900:00Delay+1h
- PiplanCrossedArrive23:3400:40Depart23:3600:44Delay+1h 06m
- AlluwaliCrossedArrive23:5501:05Depart23:5701:06Delay+1h 11m
- Kundian JnCrossedArrive00:25 +1d01:31Depart00:45 +1d01:52Delay+1h 07m
- Mian WaliCrossedArrive01:05 +1d02:14Depart01:13 +1d02:16Delay+1h 09m
- Pai KhelCrossedArrive01:34 +1d02:48Depart01:36 +1d02:49Delay+1h 15m
- Daud Khel JnCrossedArrive01:50 +1d03:11Depart01:52 +1d03:15Delay+1h 21m
- Mukhad RoadNo recordArrive02:50 +1dDepart02:52 +1dDelay—
- InjraNo recordArrive03:12 +1dDepart03:14 +1dDelay—
- ChhabCrossedArrive03:35 +1d04:55Depart03:37 +1d04:57Delay+1h 20m
- JhammatNo recordArrive03:53 +1dDepart03:55 +1dDelay—
- Jand JnCrossedArrive04:30 +1d05:43Depart04:32 +1d05:47Delay+1h 13m
- NammalNo recordArrive04:53 +1dDepart04:54 +1dDelay—
- DomelCrossedArrive05:09 +1d06:16Depart05:10 +1d06:22Delay+1h 08m
- Basal JnCrossedArrive05:21 +1d06:25Depart05:23 +1d06:28Delay+1h 04m
- Basal SharifCrossedArrive05:29 +1d06:32Depart05:30 +1d06:34Delay+1h 03m
- Fateh JangCrossedArrive06:09 +1d07:16Depart06:11 +1d07:18Delay+1h 07m
- TarnoulNo recordArrive06:37 +1dDepart06:39 +1dDelay—
- Golra SharifNo recordArrive06:47 +1dDepart06:50 +1dDelay—
- RawalpindiNo recordArrive07:15 +1dDepart—Delay—
Recorded times come from Pakistan Railways’ control room or from the train’s GPS.
The shape of the run
from the GPS trailWhere this run lost time, where it stood at a stop, and where its tracker went dark — the same journey as the table above, drawn from the raw position trail.
1,440 GPS positions recorded between 23 Aug 16:41 and 24 Aug 07:54 PKT · 28 of 37 scheduled stops have a recorded time.
How fast it was going
km along the route — route distance from traced track geometry; 0 of 36 stop-to-stop segments measured straight-line.
How late it was running — each step is a station
How long it stopped at each scheduled stop
What the marks mean
- A blank means the train’s tracker stopped reporting — it does not mean the train stopped or anything happened to it. 6 gaps on this run, 50 min total.
- 0 readings above 120 km/h, 0 not corroborated by the position trail. All values shown as recorded.
- Grey bar: how long the timetable allows here. Coloured bar: how long it actually stopped, with the figure printed under it. A stand longer than the scale is drawn capped and marked ▲ — the printed figure is always the recorded one. A dash means how long it stood there is unknown — not zero: either no departure was recorded, or the two recorded clocks contradict each other.
- An unwitnessed stop breaks the lateness line — it does not interpolate across it.
- Route distance is measured from traced track geometry where we have it, straight line between the two stations otherwise.
The upper trace above is recorded GPS positions; the lower trace is recorded station crossings — the same crossings shown in the table near the top of this page. A gap in one trace is not a gap in the other.