Hyderabad Jn to Faisalabad
Shalimar Express 27UP — within 15 minutes of the scheduled time 20% of the time, typically 57 minutes late, over 7 days of recorded runs across every stop of its full journey, not this segment alone.
Every train, compared
3 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Hyderabad Jn and Faisalabad on the same run — not how late it arrives; a train can run late through its whole journey and still show no change here. — means either too few recorded runs on this leg, or — permanently, for a train whose journey starts right here at Hyderabad Jn — no booked arrival at Hyderabad Jn to measure from at all. Figures cover runs recorded between 30 July 2026 and 29 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 27Shalimar Express 27UP | 09:25 | 23:25 | 14h | 983 km | +57 min | 20% | no data |
| 47Rehman Baba Express 47UP | 14:55 | 06:55 +1d | 16h | 979 km | +1h 32m | 11% | adds 1h 37m · 37 |
| 45Pakistan Express 45UP | 16:48 | 09:30 +1d | 16h 42m | 977 km | — | — | adds 1h 14m · 31 |
| 41Karakoram Express 41UP | 17:40 | 07:35 +1d | 13h 55m | 931 km | — | — | no data |
| 17Millat Express 17UP | 19:48 | 12:00 +1d | 16h 12m | 934 km | +3h 34m | 0% | adds 1h 10m · 38 |
| 43Shah Hussain Express 43UP | 23:35 | 13:20 +1d | 13h 45m | not measured yet | — | — | no data |
| 35Sir Sayyed Express 35UP | 23:45 | 14:00 +1d | 14h 15m | not measured yet | — | — | no data |
What the marks mean
- Departs · Arrives — scheduled local times, published Pakistan Railways timetable
- +1d — a stop on a later day of the train's own run, not a date
- Typical delay · On-time — the train's whole journey, not this segment alone; typical is the median of its recorded stop arrivals, and on-time is within 15 minutes of the scheduled time
- — — fewer than 7 days of recorded runs for that train
- Over this leg — the change in each train's delay between the two stations above, counted on runs recorded at both (a run whose two stations were logged a day apart is matched too, when that day-shifted leg length matches the train's usual one). “adds” means the train picked up extra delay over this stretch; “makes up” means it arrived less late than it left; “no change” means neither. The figure shown is the middle (median) run: no more than half of a train's counted runs did WORSE than it, and no more than half did better — never a claim that exactly half did either, which isn't always possible to state.
- A large “makes up” usually says more about the leg than the train: where several services on this page all recover time, the stretch is booked with room in it. It never means the train ran early — only that it was less late arriving than departing.
- — — in that column: fewer than 7 runs recorded at both stations on the leg's usual booked times, or — permanently, for a train whose journey starts at this page's origin station — no booked arrival there to measure from at all, which will not fill in with more archive age.
Every service in detail
Typical delay and on-time share are the train's whole journey, from 7+ days of recorded runs. Over this leg is the change in that train's delay between the two stations, from runs recorded at both.
- Shalimar Express 27UP27شالیمار ایکسپریس 27 اپ09:25→23:2514h20% on time · +57 minno data over this leg
- Rehman Baba Express 47UP47رحمان بابا ایکسپریس47اپ14:55→06:55 +1d16h11% on time · +1h 32madds 1h 37m over this leg · 37 runs
- Pakistan Express 45UP45پاکستان ایکسپریس 45 اپ16:48→09:30 +1d16h 42mno delay figure yetadds 1h 14m over this leg · 31 runs
- Karakoram Express 41UP41قراقرم ایکسپریس 41 اپ17:40→07:35 +1d13h 55mno delay figure yetno data over this leg
- Millat Express 17UP17ملت ایکسپریس 17 اپ19:48→12:00 +1d16h 12m0% on time · +3h 34madds 1h 10m over this leg · 38 runs
- Shah Hussain Express 43UP43شاہ حسین ایکسپریس 43اپ23:35→13:20 +1d13h 45mno delay figure yetno data over this leg
- Sir Sayyed Express 35UP35سر سید ایکپریس 35اپ23:45→14:00 +1d14h 15mno delay figure yetno data over this leg
Travelling the other way? Faisalabad to Hyderabad Jn trains →
Common questions
How many trains run from Hyderabad Jn to Faisalabad?
7 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Hyderabad Jn to Faisalabad?
Shah Hussain Express 43UP, booked at 13h 45m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Hyderabad Jn to Faisalabad is most likely to be on time?
Shalimar Express 27UP has the best recorded punctuality of the services we hold enough history for: 20% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 57 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 3 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Hyderabad Jn to Faisalabad?
Yes. 6 of the 7 scheduled services are booked to arrive on a later day than they depart: Rehman Baba Express 47UP, Pakistan Express 45UP, Karakoram Express 41UP, Millat Express 17UP and others.
Do trains lose time between Hyderabad Jn and Faisalabad?
Typically yes. Rehman Baba Express 47UP adds about 1h 37m to its delay over this leg, measured across 37 recorded runs. That is the CHANGE over the leg, not how late the train arrives: a train can run late its whole journey and add nothing here.
How far is it from Hyderabad Jn to Faisalabad by train?
It is between 931 and 983 km along the track, depending on the service. Measured by summing our own GPS traces of trains running the route, not the straight-line distance between the two stations, which is always shorter than the rails. That is measured on 5 of the 7 services; the rest of the track on this route has not been traced yet.
Are these Hyderabad Jn to Faisalabad timings the real arrival times?
No. The departure and arrival columns are what the published timetable books. The delay columns beside them are what we recorded actually happening, from the operator's own reports and from GPS traces of the trains. Where a delay figure is blank we do not yet hold enough recorded runs to publish one.