latetrains.pkLate, on record49 live
Trains/Margala–Jacobabad/TEST ENG 1134 DN

1134 TEST ENG اسلام آباد ٹو تہران استنبول کنٹینر(آئ ٹی آئی )ڈاؤن

Kitni late hoti hai? Typical delay, on-time record aur station timings.
MARGALAJACOBABADMARGALA
Down direction · returnsمارگلہ ۔ جیکب آباد ۔ مارگلہ
Last seen 9 October 202669 days trackedLatest run →

How late is it, usually?

no figure yet
Since 1 August 2026

5 days 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
5 / 7
Positions logged
39,510
Stops timed
8

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

Where the time goes

most of it lost after Rawalpindi

Leaves Rawalpindi +1h 50m · reaches Lahore Jn. +8h 34m — +6h 44m lost along the way.

  1. Margala16:00مارگلہ—
  2. Rawalpindi19:00راولپِنڈى+1h 50m
  3. Lala Musa Jn.02:30لالہ مُوسٰی جنکشن—
  4. Wazirabad Jn04:05وزیرآباد جنکشن+10h 01m
  5. Lahore Jn.13:00لاہور جنکشن+8h 34m
  6. Khanewal Jn01:00خانیوال—
  7. Samasata Jn06:00سمہ سٹہ جنکشن—
  8. Rohri Jn.17:30روہڑی جنکشن—
  9. Jacobabad Jn08:00جیکب آباد—
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
  • Most time is lost between Rawalpindi and Wazirabad Jn (+8h 11m)
  • Every stop on the current timetable is listed, in order, measured or not.

Timetable

scheduled → actual, 7 October 2026 run

The second time in a cell is what actually happened on the 7 October 2026 run.

#StationArrivalDeparture
1Margala—16:00
2Rawalpindi17:0019:00
3Lala Musa Jn.01:30 +1d02:30 +1d
4Wazirabad Jn04:00 +1d04:05 +1d
5Lahore Jn.09:00 +1d → 21:19·PR13:00 +1d → 21:29
6Khanewal Jn00:00 +2d01:00 +2d
7Samasata Jn05:00 +2d06:00 +2d
8Rohri Jn.16:00 +2d17:30 +2d
9Jacobabad Jn21:30 +2d08:00 +2d
What the marks mean
  • → 21:28 — actual time on the 7 October 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

Station by station, last 5 days

12 arrivals recorded

One mark per day, newest first.

Days shownFri9 OctWed7 OctTue6 OctSat3 OctFri2 Oct

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

  • 2Rawalpindischeduled 17:00+10m1 day
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Wed 7 Octnot recorded—
    Tue 6 Octnot recorded—
    Sat 3 Oct19:09+10mPakistan Railways
    Fri 2 Octnot recorded—

    Seen on 1 of 5 days. Every train at Rawalpindi →

  • 4Wazirabad Jnscheduled 04:00+10h012 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Wed 7 Octarrived, time not recorded—Pakistan Railways
    Tue 6 Octnot recorded—
    Sat 3 Octnot recorded—
    Fri 2 Octarrived, time not recorded+10h01Pakistan Railways

    Seen on 2 of 5 days. Every train at Wazirabad Jn →

  • 5Lahore Jn.scheduled 09:00+10h404 days
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Wed 7 Oct21:19—Pakistan Railways
    Tue 6 Octarrived, time not recorded—Pakistan Railways
    Sat 3 Octarrived, time not recorded—Pakistan Railways
    Fri 2 Oct19:39+10h40Train GPS

    Seen on 4 of 5 days. Every train at Lahore Jn. →

  • 6Khanewal Jnscheduled 00:00—no figure
    DayArrivedDelayRecorded by
    Fri 9 Octnot recorded—
    Wed 7 Octnot recorded—
    Tue 6 Octarrived, time not recorded—Pakistan Railways
    Sat 3 Octarrived, time not recorded—Pakistan Railways
    Fri 2 Octnot recorded—

    Seen on 2 of 5 days. Every train at Khanewal Jn →

  • 7Samasata Jnscheduled 05:00—no figure
    DayArrivedDelayRecorded by
    Fri 9 Octarrived, time not recorded—Pakistan Railways
    Wed 7 Octarrived, time not recorded—Pakistan Railways
    Tue 6 Octnot recorded—
    Sat 3 Octnot recorded—
    Fri 2 Octnot recorded—

    Seen on 2 of 5 days. Every train at Samasata Jn →

  • 8Rohri Jn.scheduled 16:00—no figure
    DayArrivedDelayRecorded by
    Fri 9 Oct07:03—Pakistan Railways
    Wed 7 Octnot recorded—
    Tue 6 Octnot recorded—
    Sat 3 Octnot recorded—
    Fri 2 Octnot recorded—

    Seen on 1 of 5 days. Every train at Rohri Jn. →

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.
  • 2 further stops on this route with nothing recorded yet — not listed.

Common questions

What time does TEST ENG 1134 DN leave Margala?

16:00, on the current published timetable. It is booked into Jacobabad Jn at 21:30, two days after it leaves. Those are booked times. The delay figures on this page are what we recorded against them.

How long does TEST ENG 1134 DN take from Margala to Jacobabad Jn?

53h 30m on the timetable. We do not yet hold enough recorded arrivals at Jacobabad Jn to say what it takes in practice.

How many stops does TEST ENG 1134 DN make?

9 on the current published timetable, from Margala to Jacobabad Jn. 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.

Where is TEST ENG 1134 DN right now?

The live tracker for this train shows its last reported position and how late it was running at its most recent recorded stop. Position comes from the operator's own feed. When a train is not reporting we say so rather than estimating where it might be.