Train Arriva 18962 Aachen Hbf – Liège-Guillemins

Aachen Hbf 19:17 → Liège-Guillemins 20:50 Daily 1 h 33 min · 14 stops Arriva

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 19:17 from Aachen Hbf · Thu 5 Nov

Next departure 19:17 today · Aachen Hbf
On-time · 30 days
40%
2/5 runs under 3 min
RT coverage: 3 full · 2 partial · 4 no data
On-time · 90 days
40%
2/5 runs under 3 min
RT coverage: 3 full · 2 partial · 28 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Liège-Guillemins, in minutes. One bar per run.

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

Worst days

  • Sun 11 Oct Max en route +7 min · last fix heading to Meerssen +6 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Meerssen +4 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Eijsden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 40% · 2
  • 3–10 min 60% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 0% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 5 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
19:17on time on time
19:20 / 19:21— —
19:29 / 19:31— —
19:35— —
19:38 / 19:43— —
19:47 / 19:49— —
20:00— —
20:05— —
20:11 / 20:16— —
20:18 / 20:20— —
20:26 / 20:27— —
20:32 / 20:33— —
20:42 / 20:43— —
20:50— —

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 NovEijsden 20:39Partial coverage0 min—
Sat 31 OctEijsden 20:46Partial coverage+3 min+5 min
Sun 25 OctMeerssen 20:22No data—
Sat 24 OctMeerssen 20:55No data—
Sun 18 OctMeerssen 20:22+3 min+3 min
Sat 17 OctMeerssen 20:20No data—
Fri 16 OctHeerlen 20:03No data—
Sun 11 OctMeerssen 20:27+6 min+7 min
Sat 10 OctMeerssen 20:24+4 min+4 min
Sun 4 OctMeerssen 20:21No data—
Sat 3 OctMeerssen 20:26No data—
Sun 27 SeptMeerssen 20:27No data—
Sat 26 SeptMeerssen 20:21No data—
Sun 20 SeptEijsden 20:41No data—
Sat 19 SeptEijsden 21:03No data—
Sun 13 SeptEijsden 20:42No data—
Sat 12 SeptEijsden 20:41No data—
Sun 6 SeptEijsden 20:43No data—
Sun 30 AugEijsden 20:42No data—
Sat 29 AugEijsden 20:41No data—
Sun 23 AugEijsden 20:46No data—
Sat 22 AugEijsden 20:42No data—
Fri 21 AugEijsden 20:41No data—
Mon 17 AugLandgraaf 19:57No data—
Sun 16 AugLandgraaf 19:58No data—
Sat 15 AugLandgraaf 20:00No data—
Fri 14 AugLandgraaf 19:57No data—
Thu 13 AugLandgraaf 19:57No data—
Wed 12 AugLandgraaf 19:53No data—
Tue 11 AugLandgraaf 19:57No data—