Rawalpindi to Ghotki
Jaffar Express 40DN — within 15 minutes of the scheduled time 25% of the time, typically 50 minutes late, over 11 days of recorded runs across every stop of its full journey, not this segment alone. That is its whole-journey record, a different promise from this leg alone: over just Rawalpindi to Ghotki it typically adds 1h 11m, from 31 recorded runs. At Ghotki it has typically arrived 82 minutes late, from 32 recorded runs.
Every train, compared
7 of 7 with 7+ daysOver this leg is the CHANGE in a train's delay between Rawalpindi and Ghotki 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 Rawalpindi — no booked arrival at Rawalpindi to measure from at all. Figures cover runs recorded between 30 July 2026 and 6 October 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 2Khyber Mail 2DN | 01:50 +1d | 19:45 +1d | 17h 55m | 1,035 km | +2h 09m | 6% | no data |
| 46Pakistan Express 46DN | 06:00 | 22:54 | 16h 54m | 964 km | +1h 05m | 6% | no data |
| 8Tezgam 8DN | 08:00 | 00:23 +1d | 16h 23m | 1,019 km | +52 min | 18% | no data |
| 40Jaffar Express 40DN | 10:35 | 03:23 +1d | 16h 48m | 1,031 km | +50 min | 25% | adds 1h 11m · 31 |
| 14Awam Express 14DN | 12:30 | 07:30 +1d | 19h | 1,036 km | +2h 03m | 8% | adds 1h 59m · 31 |
| 48Rehman Baba Express 48DN | 14:40 | 06:27 +1d | 15h 47m | 1,375 km | +2h 18m | 13% | adds 2h 15m · 33 |
| 12Hazara Express 12DN | 17:10 | 13:36 +1d | 20h 26m | 984 km | +1h 21m | 10% | adds 1h 01m · 23 |
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.
- Khyber Mail 2DN2خیبر میل 2 ڈائون01:50 +1d→19:45 +1d17h 55m6% on time · +2h 09mno data over this leg
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون06:00→22:5416h 54m6% on time · +1h 05mno data over this leg
- Tezgam 8DN8تیزگام 8 ڈاؤن08:00→00:23 +1d16h 23m18% on time · +52 minno data over this leg
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون10:35→03:23 +1d16h 48m25% on time · +50 minadds 1h 11m over this leg · 31 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون12:30→07:30 +1d19h8% on time · +2h 03madds 1h 59m over this leg · 31 runs
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن14:40→06:27 +1d15h 47m13% on time · +2h 18madds 2h 15m over this leg · 33 runs
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن17:10→13:36 +1d20h 26m10% on time · +1h 21madds 1h 01m over this leg · 23 runs
Travelling the other way? Ghotki to Rawalpindi trains →
Common questions
How many trains run from Rawalpindi to Ghotki?
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 Rawalpindi to Ghotki?
Rehman Baba Express 48DN, booked at 15h 47m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Rawalpindi to Ghotki is most likely to be on time?
Jaffar Express 40DN has the best recorded punctuality of the services we hold enough history for: 25% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 50 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 7 of 7 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Rawalpindi to Ghotki?
Yes. 5 of the 7 scheduled services are booked to arrive on a later day than they depart: Tezgam 8DN, Jaffar Express 40DN, Awam Express 14DN, Rehman Baba Express 48DN and others.
Do trains lose time between Rawalpindi and Ghotki?
Typically yes. Rehman Baba Express 48DN adds about 2h 15m to its delay over this leg, measured across 33 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 Rawalpindi to Ghotki by train?
It is between 964 and 1,375 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.
Are these Rawalpindi to Ghotki 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.