latetrains.pkLate, on record42 live
Trains/Fareed Express 38DN/22 August 2026

Fareed Express 38DN — the run of 22 August 2026

The recorded journey of the run that departed Saturday 22 August 2026.
RouteLahore Jn. → Karachi City
First recordedWalton, 06:26+12 min — names where it was first seen, not necessarily its origin
At Karachi Citythe record stops before Karachi City — last recorded at Karachi Cantt

The record stops before Karachi City — last recorded at Karachi Cantt at 08:47.

Every recorded crossing

this run only
Show the 43 earlier stops
  1. Lahore Jn.No recordArrive—Depart06:00Delay—
  2. WaltonCrossedArrive06:1506:26Depart06:1706:30Delay+12 min
  3. Kot LakhpatCrossedArrive06:2506:37Depart06:2706:41Delay+13 min
  4. Raiwind Jn.CrossedArrive06:5007:09Depart06:5507:13Delay+20 min
  5. Kasur JnCrossedArrive07:2507:47Depart08:0508:23Delay+23 min
  6. KhudianCrossedArrive08:3108:54Depart08:3309:00Delay+24 min
  7. UsmanwalaCrossedArrive08:4509:17Depart08:4709:20Delay+32 min
  8. KanganpurCrossedArrive09:0709:40Depart09:0909:43Delay+34 min
  9. Mandi AhmadabadCrossedArrive09:2610:03Depart09:2810:10Delay+37 min
  10. BasirpurCrossedArrive09:4810:32Depart09:5010:38Delay+45 min
  11. Haveli WasawewalaCrossedArrive10:1011:00Depart10:1211:05Delay+51 min
  12. PakpattanCrossedArrive11:1011:50Depart11:2512:13Delay+41 min
  13. Murad ChishtiCrossedArrive11:4512:30Depart11:4712:33Delay+46 min
  14. Arif WalaNo recordArrive12:05Depart12:10Delay—
  15. GagooCrossedArrive12:3413:18Depart12:3613:20Delay+45 min
  16. Mandi BurewalaCrossedArrive12:5513:37Depart13:0013:42Delay+43 min
  17. MachhianwalaCrossedArrive13:1713:59Depart13:1914:01Delay+42 min
  18. VihariCrossedArrive13:3514:21Depart13:4014:25Delay+46 min
  19. Nur ShahCrossedArrive14:0014:42Depart14:0214:56Delay+42 min
  20. MailsiCrossedArrive14:2015:13Depart14:2515:17Delay+53 min
  21. Kahror PakkaCrossedArrive14:5715:48Depart15:0215:52Delay+51 min
  22. JamraniwahCrossedArrive15:2416:09Depart15:2616:11Delay+45 min
  23. Lodhran JnCrossedArrive15:4416:27Depart15:4616:30Delay+44 min
  24. BahawalpurCrossedArrive16:1316:46Depart16:1816:53Delay+34 min
  25. Samasata JnCrossedArrive16:3517:07Depart17:0017:37Delay+33 min
  26. MubarakpurCrossedArrive17:2017:54Depart17:2217:57Delay+34 min
  27. Dera Nawab SahibCrossedArrive17:3718:10Depart17:3918:13Delay+34 min
  28. LiaquatpurCrossedArrive18:0918:42Depart18:1118:48Delay+34 min
  29. Khanpur Jn.CrossedArrive18:5019:20Depart18:5519:28Delay+30 min
  30. Rahim Yar KhanCrossedArrive19:2720:09Depart19:2920:18Delay+42 min
  31. SadiqabadCrossedArrive19:4920:40Depart19:5120:45Delay+52 min
  32. Mirpur MatheloCrossedArrive20:4821:38Depart20:5021:44Delay+51 min
  33. GhotkiCrossedArrive21:2222:05Depart21:2422:10Delay+43 min
  34. Rohri Jn.CrossedArrive22:3523:04Depart23:0023:39Delay+29 min
  35. MehrabpurCrossedArrive00:01 +1d00:56Depart00:03 +1d00:59Delay+55 min
  36. Bhiria RoadCrossedArrive00:24 +1d01:21Depart00:26 +1d01:23Delay+57 min
  37. PadidanCrossedArrive00:39 +1d01:37Depart00:41 +1d01:41Delay+59 min
  38. Nawabshah Jn.CrossedArrive02:02 +1d02:44Depart02:04 +1d02:47Delay+42 min
  39. ShahdadpurCrossedArrive03:02 +1d03:20Depart03:04 +1d03:22Delay+18 min
  40. Tando AdamCrossedArrive03:35 +1d03:44Depart03:37 +1d03:48Delay+9 min
  41. Hyderabad JnCrossedArrive04:25 +1d04:37Depart04:35 +1d05:07Delay+12 min
  42. Kotri JnCrossedArrive04:55 +1d05:24Depart04:57 +1d05:30Delay+29 min
  43. Landhi Jn.CrossedArrive06:38 +1d07:52Depart06:40 +1d07:55Delay+1h 14m
  1. Drigh RoadCrossedArrive07:16 +1d08:21Depart07:18 +1d08:28Delay+1h 06m
  2. Karachi CanttCrossedArrive07:55 +1d08:47Depart08:10 +1d09:01Delay+52 min
  3. Karachi CityNo recordArrive08:20 +1dDepart—Delay—

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.

4,719 GPS positions recorded between 22 Aug 06:08 and 23 Aug 09:01 PKT · 43 of 46 scheduled stops have a recorded time.

How fast it was going

km along the route — route distance from traced track geometry; 2 of 45 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. 3 gaps on this run, 40 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.