latetrains.pkLate, on record43 live
Trains/Fareed Express 37UP/21 August 2026

Fareed Express 37UP — the run of 21 August 2026

The recorded journey of the run that departed Friday 21 August 2026.
RouteKarachi City → Lahore Jn.
First recordedKarachi Cantt, 20:07+27 min — names where it was first seen, not necessarily its origin
At Lahore Jn.23:48+1h 43m

Reached Lahore Jn. at 23:48 on 22 August 2026, 103 minutes late — from the operator's recorded crossing.

Every recorded crossing

this run only
Show the 43 earlier stops
  1. Karachi CityNo recordArrive—Depart19:30Delay—
  2. Karachi CanttCrossedArrive19:4020:07Depart19:5020:23Delay+27 min
  3. Drigh RoadCrossedArrive20:1220:35Depart20:1320:37Delay+23 min
  4. Landhi Jn.CrossedArrive20:35Depart20:3720:53Delay+19 min
  5. Kotri JnCrossedArrive22:2522:55Depart22:2722:59Delay+31 min
  6. Hyderabad JnCrossedArrive22:4523:15Depart23:0023:23Delay+31 min
  7. Tando AdamCrossedArrive00:01 +1d00:16Depart00:03 +1d00:19Delay+16 min
  8. ShahdadpurCrossedArrive00:20 +1d00:39Depart00:22 +1d00:42Delay+20 min
  9. Nawabshah Jn.CrossedArrive00:52 +1d01:20Depart00:55 +1d01:25Delay+28 min
  10. PadidanCrossedArrive01:40 +1d02:31Depart01:42 +1d02:33Delay+52 min
  11. Bhiria RoadCrossedArrive01:55 +1d02:46Depart01:57 +1d02:50Delay+52 min
  12. MehrabpurCrossedArrive02:20 +1d03:14Depart02:22 +1d03:17Delay+54 min
  13. Rohri Jn.CrossedArrive04:35 +1d04:26Depart05:00 +1d05:04Delayon time
  14. GhotkiCrossedArrive05:41 +1d07:01Depart05:43 +1d07:08Delay+1h 20m
  15. Mirpur MatheloCrossedArrive06:07 +1d07:28Depart06:09 +1d07:31Delay+1h 21m
  16. SadiqabadCrossedArrive06:58 +1d08:32Depart07:00 +1d08:36Delay+1h 35m
  17. Rahim Yar KhanCrossedArrive07:30 +1d08:55Depart07:32 +1d08:59Delay+1h 26m
  18. Khanpur Jn.CrossedArrive09:20 +1d09:47Depart09:25 +1d09:57Delay+28 min
  19. LiaquatpurCrossedArrive09:58 +1d10:26Depart10:00 +1d10:28Delay+28 min
  20. Dera Nawab SahibCrossedArrive10:30 +1d10:57Depart10:32 +1d11:23Delay+28 min
  21. MubarakpurCrossedArrive10:48 +1d11:37Depart10:50 +1d11:41Delay+50 min
  22. Samasata JnCrossedArrive11:15 +1d12:00Depart11:40 +1d12:37Delay+45 min
  23. BahawalpurCrossedArrive11:55 +1d12:52Depart12:00 +1d12:57Delay+58 min
  24. Lodhran JnCrossedArrive12:18 +1d13:14Depart12:20 +1d13:18Delay+57 min
  25. JamraniwahCrossedArrive12:34 +1d13:34Depart12:36 +1d13:37Delay+1h
  26. Kahror PakkaCrossedArrive12:55 +1d13:53Depart13:00 +1d14:01Delay+58 min
  27. MailsiCrossedArrive13:35 +1d14:32Depart13:40 +1d14:37Delay+57 min
  28. Nur ShahCrossedArrive13:55 +1d14:54Depart13:57 +1d14:58Delay+1h
  29. VihariCrossedArrive14:25 +1d15:15Depart14:30 +1d15:20Delay+51 min
  30. MachhianwalaCrossedArrive14:47 +1d15:39Depart14:49 +1d15:42Delay+53 min
  31. Mandi BurewalaCrossedArrive15:05 +1d15:58Depart15:10 +1d16:04Delay+54 min
  32. GagooCrossedArrive15:27 +1d16:20Depart15:29 +1d16:23Delay+53 min
  33. Arif WalaCrossedArrive15:55 +1d16:48Depart16:00 +1d16:52Delay+53 min
  34. Murad ChishtiCrossedArrive16:18 +1d17:09Depart16:20 +1d17:11Delay+51 min
  35. PakpattanCrossedArrive16:45 +1d17:29Depart17:00 +1d17:48Delay+45 min
  36. Haveli WasawewalaCrossedArrive17:42 +1d18:34Depart17:44 +1d18:38Delay+53 min
  37. BasirpurCrossedArrive18:04 +1d18:59Depart18:06 +1d19:02Delay+55 min
  38. Mandi AhmadabadCrossedArrive18:26 +1d19:24Depart18:28 +1d19:28Delay+58 min
  39. KanganpurCrossedArrive18:46 +1d19:46Depart18:48 +1d19:48Delay+1h
  40. UsmanwalaCrossedArrive19:07 +1d20:10Depart19:10 +1d20:14Delay+1h 04m
  41. KhudianCrossedArrive19:28 +1d20:30Depart19:30 +1d20:33Delay+1h 03m
  42. Kasur JnCrossedArrive20:05 +1d21:06Depart20:45 +1d22:05Delay+1h 01m
  43. Raiwind Jn.CrossedArrive21:10 +1d22:37Depart21:15 +1d22:43Delay+1h 28m
  1. Kot LakhpatCrossedArrive21:40 +1d23:17Depart21:42 +1d23:21Delay+1h 37m
  2. Lahore Jn.CrossedArrive22:05 +1d23:48Depart—00:39Delay+1h 43m

Recorded times come from Pakistan Railways’ control room or from the train’s GPS.

The shape of the run

from the GPS trail

Where 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.

2,098 GPS positions recorded between 21 Aug 19:57 and 23 Aug 00:39 PKT · 43 of 45 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 0 of 44 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. 4 gaps on this run, 54 min total.
  • 1 reading 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.