Rawalpindi to Chaklala
Islamabad Express 108DN — within 15 minutes of the scheduled time 68% of the time, typically 2 minutes late, over 10 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 Chaklala it typically adds 1 min, from 29 recorded runs. At Chaklala it has typically arrived 10 minutes late, from 39 recorded runs.
Every train, compared
6 of 6 with 7+ daysOver this leg is the CHANGE in a train's delay between Rawalpindi and Chaklala 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 September 2026. why a delay figure changes along the route.
| Train | Departs | Arrives | Duration | Distance | Typical delay | On-time | Over this leg |
|---|---|---|---|---|---|---|---|
| 102Subak Raftar 102DN | 07:00 | 07:08 | 8 min | 5.6 km | +23 min | 41% | no data |
| 8Tezgam 8DN | 08:00 | 08:09 | 9 min | 5.6 km | +52 min | 18% | no data |
| 6Green Line 6DN | 15:40 | 15:50 | 10 min | 5.6 km | +43 min | 37% | makes up 1 min · 26 |
| 104Subak Kharam 104DN | 16:30 | 16:38 | 8 min | 5.6 km | +41 min | 28% | no data |
| 12Hazara Express 12DN | 17:10 | 17:19 | 9 min | 5.6 km | +1h 21m | 10% | adds 4 min · 23 |
| 108Islamabad Express 108DN | 18:00 | 18:08 | 8 min | 5.6 km | +2 min | 68% | adds 1 min · 29 |
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.
- Subak Raftar 102DN102سبک رفتار102 ڈاؤن07:00→07:088 min41% on time · +23 minno data over this leg
- Tezgam 8DN8تیزگام 8 ڈاؤن08:00→08:099 min18% on time · +52 minno data over this leg
- Green Line 6DN6گرين لائن 6 ڈاؤن15:40→15:5010 min37% on time · +43 minmakes up 1 min over this leg · 26 runs
- Subak Kharam 104DN104سبک خرام 104 ڈاؤن16:30→16:388 min28% on time · +41 minno data over this leg
- Hazara Express 12DN12ہزارا ایکسپریس 12ڈاؤن17:10→17:199 min10% on time · +1h 21madds 4 min over this leg · 23 runs
- Islamabad Express 108DN108اسلام آباد ایکسپریس 108ڈاؤن18:00→18:088 min68% on time · +2 minadds 1 min over this leg · 29 runs
Travelling the other way? Chaklala to Rawalpindi trains →
Common questions
How many trains run from Rawalpindi to Chaklala?
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 Rawalpindi to Chaklala?
Subak Raftar 102DN, booked at 8 min 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 Chaklala is most likely to be on time?
Islamabad Express 108DN has the best recorded punctuality of the services we hold enough history for: 68% of its recorded stop arrivals were within 15 minutes of schedule, with a typical delay of 2 min. That is its record across every stop of its full journey, not this leg alone. Measured from recorded runs, not from the timetable. 6 of 6 services on this route currently have enough recorded history to rank at all.
Is there an overnight train from Rawalpindi to Chaklala?
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 Chaklala?
Typically yes. Hazara Express 12DN adds about 4 min to its delay over this leg, measured across 23 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 Chaklala by train?
It is about 6 km along the track. 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 Chaklala 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.