London Overground 879I24 New Cross Gate ELL – XHZ

View line London Overground

New Cross Gate ELL 03:33 → XHZ 04:03 Sat, Sun 0 h 30 min · 13 stops London Overground

It does not run today

Last recorded run: Sunday 1 November +1 min

Next service: Saturday 03:33 from New Cross Gate ELL · Sat 7 Nov

Next departure 03:33 Saturday · New Cross Gate ELL
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 2 full · 7 partial · 0 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 2 full · 25 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at XHZ, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

27 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 4% · 1
  • On time 96% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=13
  • 100% S n=13

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 stops).

Last 90 days, 27 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
03:33on time +1 min
03:36 / 03:37— —
03:38 / 03:39— —
03:40— —
03:42— —
03:44— —
03:46— —
03:48 / 03:49— —
03:51— —
03:53— —
03:55— —
03:58— —
04:03— —

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Sun 1 NovDalston Junction 04:06Partial coverage+1 min+1 min
Sat 31 OctHoxton 04:05Partial coverage0 min—
Mon 26 Oct— 15:210 min—
Sun 25 Oct— 04:250 min—
Sat 24 OctHoxton 04:05Partial coverage0 min—
Sun 18 OctDalston Junction 04:06Partial coverage+1 min+1 min
Sat 17 OctDalston Junction 04:06Partial coverage+1 min+2 min
Sun 11 OctDalston Junction 04:06Partial coverage+1 min+2 min
Sat 10 OctHoxton 04:05Partial coverage0 min—
Sun 4 Oct87660 04:05Partial coverage0 min—
Sat 3 Oct87660 04:05Partial coverage0 min—
Sun 27 Sept87660 04:05Partial coverage0 min—
Sat 26 Sept87660 04:04Partial coverage−1 min—
Sun 20 Sept87660 04:20Partial coverage−4 min+6 min
Sat 19 Sept87660 04:05Partial coverage0 min—
Sun 13 Sept87660 04:06Partial coverage+1 min+1 min
Sat 12 Sept87660 04:05Partial coverage−1 min—
Sun 6 Sept87660 04:06Partial coverage+1 min+2 min
Sat 5 Sept87660 04:06Partial coverage0 min+1 min
Sun 30 Aug87660 04:04Partial coverage−1 min—
Sat 29 Aug87660 04:05Partial coverage0 min+1 min
Sun 23 Aug87660 04:05Partial coverage0 min+1 min
Sat 22 Aug87660 04:06Partial coverage+1 min+2 min
Sun 16 Aug87660 04:06Partial coverage+1 min+1 min
Sat 15 Aug87660 04:05Partial coverage0 min+1 min
Sun 9 Aug87660 04:05Partial coverage0 min—
Sat 8 Aug87660 04:04Partial coverage0 min—