Train Arriva 18970 Aachen Hbf – Liège-Guillemins

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 21:17 from Aachen Hbf · Wed 18 Nov

Next departure 21:17 today · Aachen Hbf
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 3 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 3 full · 5 partial · 17 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: 0 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

  • Sat 10 Oct Max en route +3 min · last fix heading to Meerssen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 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=5

Stops and timetable

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

Last 90 days, 8 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
21:17on time on time
21:20 / 21:21— —
21:29 / 21:31— —
21:35— —
21:38 / 21:43— —
21:47 / 21:49— —
22:00— —
22:05— —
22:11 / 22:16— —
22:18 / 22:20— —
22:26 / 22:27— —
22:32 / 22:33— —
22:42 / 22:43— —
22: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 15 NovEijsden 22:39Partial coverage0 min—
Sat 14 NovEijsden 22:39Partial coverage0 min—
Sun 8 NovEijsden 22:39Partial coverage0 min—
Sat 7 NovEijsden 22:39Partial coverage0 min—
Sun 1 NovEijsden 22:39Partial coverage0 min—
Sat 31 OctEijsden 22:41No data—
Sun 25 OctMeerssen 22:22No data—
Sat 24 OctMeerssen 22:19No data—
Sun 18 OctMeerssen 22:21+1 min+1 min
Sat 17 OctMeerssen 22:26No data—
Sun 11 OctMeerssen 22:22+1 min+2 min
Sat 10 OctMeerssen 22:19+3 min+3 min
Sun 4 OctMeerssen 22:20No data—
Sat 3 OctMeerssen 22:17No data—
Sun 27 SeptMeerssen 22:20No data—
Sat 26 SeptMeerssen 22:20No data—
Sun 20 SeptEijsden 22:41No data—
Sat 19 SeptEijsden 22:41No data—
Sun 13 SeptEijsden 22:41No data—
Sat 12 SeptEijsden 22:41No data—
Sun 6 SeptEijsden 22:41No data—
Sun 30 AugEijsden 22:41No data—
Sat 29 AugEijsden 22:41No data—
Sun 23 AugEijsden 22:41No data—
Sat 22 AugEijsden 22:41No data—