Train Arriva 18965 Liège-Guillemins – Aachen Hbf

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

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: tomorrow 19:08 from Liège-Guillemins · Tue 10 Nov

Next departure 19:08 tomorrow · Liège-Guillemins
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 2 full · 4 partial · 4 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +1 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 10 Oct Max en route +9 min · last fix heading to Eygelshoven Markt +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 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
  • 67% S n=3
  • 100% S n=4

Stops and timetable

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

Last 90 days, 7 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:08on time on time
19:16 / 19:17— —
19:26 / 19:27— —
19:30— —
19:37 / 19:42— —
19:45 / 19:53— —
19:58— —
20:03— —
20:15 / 20:18— —
20:22— —
20:25— —
20:29 / 20:30— —
20:37 / 20:38— —
20: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
Sun 8 NovEygelshoven Markt 20:44Partial coverage+2 min+2 min
Sat 7 NovEygelshoven Markt 20:42Partial coverage0 min—
Sun 1 NovEygelshoven Markt 20:42Partial coverage0 min—
Sat 31 OctEygelshoven Markt 20:42Partial coverage0 min—
Sun 25 OctEygelshoven Markt 20:43No data—
Sat 24 OctEygelshoven Markt 20:55No data—
Sun 18 OctEygelshoven Markt 20:430 min—
Sat 17 OctEygelshoven Markt 20:44No data—
Fri 16 OctMaastricht 20:07No data—
Sun 11 OctEygelshoven Markt 20:420 min—
Sat 10 OctEygelshoven Markt 20:49+9 min+9 min
Sun 4 OctEygelshoven Markt 20:42No data—
Sat 3 OctEygelshoven Markt 20:43No data—
Sun 27 SeptEygelshoven Markt 20:43No data—
Sat 26 SeptEygelshoven Markt 20:44No data—
Sun 20 SeptEygelshoven Markt 20:42No data—
Sat 19 SeptEygelshoven Markt 20:44No data—
Sun 13 SeptEygelshoven Markt 20:44No data—
Sat 12 SeptEygelshoven Markt 21:06No data—
Sun 6 SeptEygelshoven Markt 20:42No data—
Sun 30 AugEygelshoven Markt 20:43No data—
Sat 29 AugEygelshoven Markt 20:44No data—
Sun 23 AugEygelshoven Markt 20:44No data—
Sat 22 AugEygelshoven Markt 20:43No data—
Fri 21 AugEygelshoven Markt 20:39No data—
Mon 17 AugMaastricht Randwyck 19:56No data—
Sun 16 AugEygelshoven Markt 20:42No data—
Sat 15 AugEygelshoven Markt 20:43No data—
Fri 14 AugEygelshoven Markt 20:38No data—
Wed 12 AugEygelshoven Markt 20:38No data—