Rawalpindi to Gujrat
Subak Raftar 102DN — within 15 minutes of the scheduled time 41% of the time, typically 23 minutes late, over 10 days of recorded runs across every stop of its full journey, not this segment alone. At Gujrat it has typically arrived 26 minutes late, from 35 recorded runs.
Every train, compared
7 of 8 with 7+ daysOver this leg is the CHANGE in a train's delay between Rawalpindi and Gujrat 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 7 September 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 | 05:02 +1d | 3h 12m | 173 km | +2h 09m | 6% | no data |
| 46Pakistan Express 46DN | 06:00 | 09:20 | 3h 20m | 175 km | +1h 05m | 6% | no data |
| 102Subak Raftar 102DN | 07:00 | 10:07 | 3h 07m | 176 km | +23 min | 41% | no data |
| 8Tezgam 8DN | 08:00 | 11:22 | 3h 22m | 176 km | +52 min | 18% | no data |
| 40Jaffar Express 40DN | 10:35 | 14:10 | 3h 35m | 175 km | +50 min | 25% | makes up 12 min · 34 |
| 14Awam Express 14DN | 12:30 | 16:10 | 3h 40m | 175 km | +2h 03m | 8% | makes up 1 min · 33 |
| 36Sir Sayyed Express 36DN | 13:30 | 16:36 | 3h 06m | not measured yet | — | — | no data |
| 104Subak Kharam 104DN | 16:30 | 19:36 | 3h 06m | 176 km | +41 min | 28% | 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.
- Khyber Mail 2DN2خیبر میل 2 ڈائون01:50 +1d→05:02 +1d3h 12m6% on time · +2h 09mno data over this leg
- Pakistan Express 46DN46پاکستان ایکسپریس 46 ڈائون06:00→09:203h 20m6% on time · +1h 05mno data over this leg
- Subak Raftar 102DN102سبک رفتار102 ڈاؤن07:00→10:073h 07m41% on time · +23 minno data over this leg
- Tezgam 8DN8تیزگام 8 ڈاؤن08:00→11:223h 22m18% on time · +52 minno data over this leg
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون10:35→14:103h 35m25% on time · +50 minmakes up 12 min over this leg · 34 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون12:30→16:103h 40m8% on time · +2h 03mmakes up 1 min over this leg · 33 runs
- Sir Sayyed Express 36DN36سر سید ایکپریس 36 ڈاؤن13:30→16:363h 06mno delay figure yetno data over this leg
- Subak Kharam 104DN104سبک خرام 104 ڈاؤن16:30→19:363h 06m28% on time · +41 minno data over this leg
Travelling the other way? Gujrat to Rawalpindi trains →
Common questions
How many trains run from Rawalpindi to Gujrat?
8 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 Gujrat?
Sir Sayyed Express 36DN, booked at 3h 06m 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 Gujrat is most likely to be on time?
Subak Raftar 102DN has the best recorded punctuality of the services we hold enough history for: 41% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 23 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 8 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Rawalpindi to Gujrat?
Not on the current timetable. Every service on this route is booked to arrive on the same day it departs.
Do trains lose time between Rawalpindi and Gujrat?
Typically the opposite. Jaffar Express 40DN makes up about 12 min over this leg across 34 recorded runs. That does not mean it runs early; it means it arrived less late than it departed, which usually says more about how the timetable books this stretch than about the train.
How far is it from Rawalpindi to Gujrat by train?
It is between 173 and 176 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 7 of the 8 services; the rest of the track on this route has not been traced yet.
Are these Rawalpindi to Gujrat 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.