latetrains.pkLate, on record35 live
Trains/Kohat–Rawalpindi/Kohat Express 134DN

134 Kohat Express 134DN کوہاٹ ایکسپریس 134ڈاؤن

Kitni late hoti hai? Typical delay, on-time record aur station timings.
KOHATRAWALPINDIKOHAT
Down direction · returnsکوہاٹ کینٹ ۔ راولپِنڈى ۔ کوہاٹ کینٹ
In service since 2018ExpressLast seen 7 September 202670 days tracked

How late is it, usually?

no figure yet
Since 1 August 2026

One day recorded so far.

A typical (median) delay figure appears at 7 full days of recorded runs — days the train reported, not calendar days.

Recorded days
1 / 7
Positions logged
13,918
Stops timed
10

1 of 7 recorded days toward a first typical-delay figure

Where the time goes

runs close to time

Leaves Babari Banda 2 min early · reaches Rawalpindi +6 min — +8 min lost along the way.

  1. Kohat Cantt07:30کوہاٹ کینٹ—
  2. Babari Banda07:55بابری بانڈہ2 min early
  3. Jand Jn09:06جنڈ جنکشن+1 min
  4. Domel09:31ڈومیل+4 min
  5. Basal Jn09:44بسال جنکشن+2 min
  6. Basal Sharif09:51بسال شریفon time
  7. Kahal10:00کیہلon time
  8. Fateh Jang10:36فتح جنگ2 min early
  9. Tarnoul11:05ترنول+5 min
  10. Golra Sharif11:17گولڑہ شریف+3 min
  11. Rawalpindi11:35راولپِنڈى+6 min

Where it stands longest past the timetableshortest to longest recorded

  1. Fateh Jangscheduled 2 min3–18 min
  2. Jand Jnscheduled 2 min3–14 min
  3. Domelscheduled 1 min1–3 min
  4. Basal Jnscheduled 2 min1–7 min
  5. Basal Sharifscheduled 1 min1–2 min
What the marks mean
  • Solid bar — the typical delay at that stop (median of recorded arrivals)
  • Faint bar behind — the bad day (90th percentile): worse than nine tenths of recorded arrivals here
  • No faint bar — fewer than 7 recorded arrivals at that stop, too thin for a 90th percentile. The solid bar can still show: it needs only 3.
  • — (no solid bar either) — fewer than 3 recorded runs at that stop
  • A negative figure means the train typically ran early at that stop, not late
  • Band — the shortest and the longest stand recorded at that stop. The train has left as early as the first figure.
  • Keyline — the scheduled stop, arrival to departure on the timetable below.
  • Why a train stands is not recorded — a crossing, a loco change and a red signal all look the same on the clock.
  • The five stops that stand longest past the timetable, not every stop — most routes have more. A stop qualifies with 7 or more runs timed in and out, and is skipped where the timetable books no stop, books one over an hour, or where any recorded stand ran past three hours.
  • Most time is lost between Fateh Jang and Tarnoul (+7 min)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 7 September 2026 run

The second time in a cell is what actually happened on the 7 September 2026 run. See the whole run →

#StationArrivalDeparture
1Kohat Cantt—07:30
2Babari Banda07:53 → 07:5107:55 → 07:53
3Jand Jn09:04 → 09:0309:06 → 09:07
4Domel09:30 → 09:3309:31 → 09:35
5Basal Jn09:4209:44
6Basal Sharif09:5009:51
7Kahal09:59 → 09:5710:00 → 09:58
8Fateh Jang10:34 → 10:3110:36 → 10:36
9Tarnoul11:03 → 11:0911:05 → 11:11
10Golra Sharif11:14 → 11:2111:17 → 11:24
11Rawalpindi11:35—
What the marks mean
  • → 21:28 — actual time on the 7 September 2026 run
  • ·PR — Pakistan Railways' own record; unmarked is from the train's GPS
  • +1d — the stop falls on a later day of the train's own run, counting from the day it starts. It is not a date.
  • Blank — not recorded

A full recorded run: 14 August 2026 →

Station by station, last 5 days

47 arrivals recorded

One mark per day, newest first.

Days shownMon7 SeptFri14 AugThu13 AugWed12 AugTue11 Aug

A run’s GPS trail is decoded after the journey completes — recent days may link later.

  • 2Babari Bandascheduled 07:532m early5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept07:512m earlyPakistan Railways (journey record)
    Fri 14 Aug07:512m earlyPakistan Railways (journey record)
    Thu 13 Aug07:493m earlyPakistan Railways (journey record)
    Wed 12 Aug07:59+4mPakistan Railways
    Tue 11 Aug07:53on timePakistan Railways (journey record)

    Seen on 5 of 5 days, ranging 3m early to +4m. Every train at Babari Banda →

  • 3Jand Jnscheduled 09:044m early5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept09:03on timePakistan Railways (journey record)
    Fri 14 Aug08:549m earlyPakistan Railways (journey record)
    Thu 13 Aug09:004m earlyPakistan Railways (journey record)
    Wed 12 Aug09:006m earlyPakistan Railways
    Tue 11 Aug09:05+2mPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging 9m early to +2m. Every train at Jand Jn →

  • 4Domelscheduled 09:30+3m5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept09:33+4mPakistan Railways (journey record)
    Fri 14 Aug09:29on timePakistan Railways (journey record)
    Thu 13 Aug09:40+5mPakistan Railways
    Wed 12 Aug09:30on timePakistan Railways
    Tue 11 Aug09:33+3mPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging on time to +5m. Every train at Domel →

  • 5Basal Jnscheduled 09:422m early4 days
    DayArrivedDelayRecorded by
    Mon 7 Septnot recorded—
    Fri 14 Aug09:383m earlyPakistan Railways (journey record)
    Thu 13 Aug09:43+2mPakistan Railways (journey record)
    Wed 12 Aug09:395m earlyPakistan Railways
    Tue 11 Aug09:411m earlyPakistan Railways (journey record)

    Seen on 4 of 5 days, ranging 5m early to +2m. Every train at Basal Jn →

  • 6Basal Sharifscheduled 09:501m early4 days
    DayArrivedDelayRecorded by
    Mon 7 Septnot recorded—
    Fri 14 Aug09:49on timePakistan Railways (journey record)
    Thu 13 Aug09:53+1mPakistan Railways
    Wed 12 Aug09:473m earlyPakistan Railways
    Tue 11 Aug09:472m earlyPakistan Railways (journey record)

    Seen on 4 of 5 days, ranging 3m early to +1m. Every train at Basal Sharif →

  • 7Kahalscheduled 09:592m early5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept09:572m earlyPakistan Railways (journey record)
    Fri 14 Aug09:581m earlyPakistan Railways (journey record)
    Thu 13 Aug09:581m earlyPakistan Railways
    Wed 12 Aug09:562m earlyPakistan Railways
    Tue 11 Aug09:572m earlyPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging 2m early to 1m early. Every train at Kahal →

  • 8Fateh Jangscheduled 10:344m early5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept10:312m earlyPakistan Railways (journey record)
    Fri 14 Aug10:312m earlyPakistan Railways (journey record)
    Thu 13 Aug10:314m earlyPakistan Railways
    Wed 12 Aug10:306m earlyPakistan Railways
    Tue 11 Aug10:304m earlyPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging 6m early to 2m early. Every train at Fateh Jang →

  • 9Tarnoulscheduled 11:03+5m5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept11:09+7mPakistan Railways (journey record)
    Fri 14 Aug11:08+5mPakistan Railways (journey record)
    Thu 13 Aug11:07+2mPakistan Railways
    Wed 12 Aug11:11+6mPakistan Railways
    Tue 11 Aug11:06+3mPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging +2m to +7m. Every train at Tarnoul →

  • 10Golra Sharifscheduled 11:14+3m5 days
    DayArrivedDelayRecorded by
    Mon 7 Sept11:21+7mPakistan Railways (journey record)
    Fri 14 Aug11:17+3mPakistan Railways (journey record)
    Thu 13 Aug11:12+4mPakistan Railways
    Wed 12 Aug11:152m earlyPakistan Railways
    Tue 11 Aug11:15+1mPakistan Railways (journey record)

    Seen on 5 of 5 days, ranging 2m early to +7m. Every train at Golra Sharif →

  • 11Rawalpindischeduled 11:35+3m4 days
    DayArrivedDelayRecorded by
    Mon 7 Septnot recorded—
    Fri 14 Aug11:36+2mPakistan Railways (journey record)
    Thu 13 Aug11:37+2mPakistan Railways (journey record)
    Wed 12 Aug11:38+3mTrain GPS
    Tue 11 Aug11:37+3mPakistan Railways (journey record)

    Seen on 4 of 5 days, ranging +2m to +3m. Every train at Rawalpindi →

What the marks mean
  • Tap a station — each day’s arrival, delay and recorder
  • Green — within 15 minutes of the scheduled time
  • Amber — 16 to 45 minutes late
  • Red — over 45 minutes late
  • Hollow — not recorded that day
  • Grey — arrived, no delay figure
  • Dash (—) — no delay figure for this stop yet
  • Pakistan Railways — its own arrival record; Train GPS — measured from the train’s position
  • The starting station is not listed — a train does not arrive where it begins.

Common questions

Is Kohat Express 134DN usually late?

Typically 6 minutes late arriving at Rawalpindi, measured across 12 recorded arrivals (2 Aug – 14 Aug 2026). That is the median, so half its runs were better than that and half were worse. It is what we recorded happening, not what the timetable books.

How late is Kohat Express 134DN on a bad day?

On the worst one run in ten, 10 minutes late into Rawalpindi, against a typical 6 minutes late. Both come from the same 12 recorded arrivals. A bad day is not the worst day we have ever seen; it is the level one run in ten reaches or passes.

What time does Kohat Express 134DN leave Kohat Cantt?

07:30, on the current published timetable. It is booked into Rawalpindi at 11:35, the day it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does Kohat Express 134DN take from Kohat Cantt to Rawalpindi?

4h 05m on the timetable. In practice a typical run has taken 4h 10m, measured from recorded arrivals at Rawalpindi.

How many stops does Kohat Express 134DN make?

11 on the current published timetable, from Kohat Cantt to Rawalpindi. The full stop list, with the times booked at each one, is in the timetable on this page. Not every stop is recorded on every run: we publish arrivals we actually observed rather than filling the gaps.

Service history (first year, operating eras) is drawn from Wikipedia's List of Pakistan Railways trains, retrieved 15 August 2026, matched on train number. Further reading: the train's own Wikipedia article.