Train Arriva 18957 Liège-Guillemins – Aachen Hbf

Liège-Guillemins 17:08 → Aachen Hbf 18:42 Daily 1 h 34 min · 14 stops Arriva

It has not run yet today

Last recorded run: Saturday 7 November +2 min

Next service: today 17:08 from Liège-Guillemins · Sun 8 Nov

Next departure 17:08 today · Liège-Guillemins
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 4 full · 10 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Aachen Hbf, in minutes. One bar per run.

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

Worst days

  • Sat 31 Oct Max en route +4 min · last fix heading to Eygelshoven Markt +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 75% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
17:08on time on time
17:16 / 17:17— —
17:26 / 17:27— —
17:30— —
17:37 / 17:42— —
17:45 / 17:53— —
17:58— —
18:03— —
18:15 / 18:18— —
18:22— —
18:25— —
18:29 / 18:30— —
18:37 / 18:38— —
18:42— —

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
Sat 7 NovEygelshoven Markt 18:44Partial coverage+2 min+2 min
Fri 6 NovEygelshoven Markt 18:39Partial coverage0 min—
Thu 5 NovValkenburg 18:17No data—
Wed 4 NovValkenburg 18:17Partial coverage0 min—
Tue 3 NovValkenburg 18:17No data—
Mon 2 NovValkenburg 18:17No data—
Sun 1 NovEygelshoven Markt 18:43Partial coverage0 min—
Sat 31 OctEygelshoven Markt 18:47Partial coverage+4 min+4 min
Fri 30 OctEygelshoven Markt 18:39No data—
Thu 29 OctMeerssen 18:12No data—
Wed 28 OctValkenburg 18:17Partial coverage0 min—
Tue 27 OctValkenburg 18:17No data—
Mon 26 OctValkenburg 18:17Partial coverage0 min—
Sun 25 OctEygelshoven Markt 18:51No data—
Sat 24 OctEygelshoven Markt 18:480 min—
Fri 23 OctEygelshoven Markt 18:39No data—
Thu 22 OctEygelshoven Markt 18:39No data—
Wed 21 OctEygelshoven Markt 18:34No data—
Tue 20 OctEygelshoven Markt 18:39Partial coverage0 min—
Mon 19 OctEygelshoven Markt 18:39Partial coverage0 min—
Sun 18 OctEygelshoven Markt 18:45+2 min+2 min
Sat 17 OctEygelshoven Markt 18:43No data—
Fri 16 OctEygelshoven Markt 18:41No data—
Thu 15 OctEygelshoven Markt 18:39No data—
Tue 13 OctValkenburg 18:17Partial coverage0 min—
Sun 11 OctEygelshoven Markt 18:420 min—
Sat 10 OctEygelshoven Markt 18:45+2 min+2 min
Fri 9 OctEygelshoven Markt 18:39Partial coverage0 min—
Thu 8 OctValkenburg 18:17Partial coverage0 min—
Wed 7 OctValkenburg 18:17Partial coverage+3 min+3 min