Attock City Jn to Rawalpindi
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 Attock City Jn to Rawalpindi it typically adds 30 min, from 36 recorded runs.
Every train, compared
5 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Attock City Jn and Rawalpindi 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 Attock City Jn — no booked arrival at Attock City Jn 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 |
|---|---|---|---|---|---|---|---|
| 40Jaffar Express 40DN | 08:42 | 10:10 | 1h 28m | 82 km | +50 min | 25% | adds 30 min · 36 |
| 14Awam Express 14DN | 10:20 | 12:05 | 1h 45m | 85 km | +2h 03m | 8% | adds 19 min · 33 |
| 48Rehman Baba Express 48DN | 12:46 | 14:20 | 1h 34m | 82 km | +2h 18m | 13% | adds 12 min · 36 |
| 276Safari Train DN | 15:30 | 17:10 | 1h 40m | not measured yet | — | — | no data |
| 129Thall Express 129UP | 20:05 | 21:45 | 1h 40m | 85 km | +1h | 6% | adds 39 min · 24 |
| 2Khyber Mail 2DN | 23:45 | 01:25 +1d | 1h 40m | 82 km | +2h 09m | 6% | 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.
- Jaffar Express 40DN40جعفر ایکسپریس 40 ڈائون08:42→10:101h 28m25% on time · +50 minadds 30 min over this leg · 36 runs
- Awam Express 14DN14عوام ایکسپریس 14 ڈائون10:20→12:051h 45m8% on time · +2h 03madds 19 min over this leg · 33 runs
- Rehman Baba Express 48DN48رحمان بابا ایکسپریس 48 ڈاؤن12:46→14:201h 34m13% on time · +2h 18madds 12 min over this leg · 36 runs
- Safari Train DN276سفاری ٹرین15:30→17:101h 40mno delay figure yetno data over this leg
- Thall Express 129UP129تھل ایکسپریس 129اپ20:05→21:451h 40m6% on time · +1hadds 39 min over this leg · 24 runs
- Khyber Mail 2DN2خیبر میل 2 ڈائون23:45→01:25 +1d1h 40m6% on time · +2h 09mno data over this leg
Travelling the other way? Rawalpindi to Attock City Jn trains →
Common questions
How many trains run from Attock City Jn to Rawalpindi?
6 scheduled services on the current published timetable. That is what is booked to run, not what ran today.
Which is the fastest train from Attock City Jn to Rawalpindi?
Jaffar Express 40DN, booked at 1h 28m for the journey. That is the timetable's figure. Whether it holds on the day is what the delay columns describe.
Which train from Attock City Jn to Rawalpindi 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. 5 of 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Attock City Jn to Rawalpindi?
Yes. 1 of the 6 scheduled services is booked to arrive on a later day than it departs: Khyber Mail 2DN.
Do trains lose time between Attock City Jn and Rawalpindi?
Typically yes. Thall Express 129UP adds about 39 min to its delay over this leg, measured across 24 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 Attock City Jn to Rawalpindi by train?
It is between 82 and 85 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 6 services; the rest of the track on this route has not been traced yet.
Are these Attock City Jn to Rawalpindi 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.