Train Arriva 18922 Aachen Hbf – Liège-Guillemins

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

✓ Today’s run finished

Today, last fix heading to Eijsden at 10:42 No data

  1. Aachen Hbf09:17
  2. Herzogenrath09:29
  3. Landgraaf09:38
  4. Meerssen10:05
  5. Eijsden10:26
  6. Vise10:32
  7. Liège-Guillemins10:50

Next service: tomorrow 09:17 from Aachen Hbf · Fri 6 Nov

Next departure 09:17 tomorrow · Aachen Hbf
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 8 full · 10 partial · 11 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 8 full · 11 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Thu 8 Oct Max en route +18 min · last fix heading to Eijsden +18 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Eijsden +3 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 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=4
  • 100% W n=3
  • 67% T n=3
  • 0% F n=1
  • 100% 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
09:17on time on time
09:20 / 09:21≈ on time ≈ on time
09:29 / 09:31≈ on time ≈ on time
09:35≈ on time ≈ on time
09:38 / 09:39≈ on time ≈ on time
09:43 / 09:49≈ on time ≈ on time
10:00≈ on time ≈ +1 min
10:05≈ on time ≈ +1 min
10:11 / 10:16≈ on time ≈ +1 min
10:18 / 10:20≈ on time ≈ +1 min
10:26 / 10:27≈ on time ≈ +1 min
10:32 / 10:33≈ on time ≈ +1 min
10:42 / 10:43≈ on time ≈ +1 min
10:50on time +2 min

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
Thu 5 NovEijsden 10:42No data—
Wed 4 NovEijsden 10:39Partial coverage0 min—
Tue 3 NovEijsden 10:43No data—
Mon 2 NovEijsden 10:43No data—
Sun 1 NovEijsden 10:420 min—
Sat 31 OctEijsden 10:430 min—
Fri 30 OctEijsden 10:47No data—
Thu 29 OctEijsden 10:41Partial coverage0 min—
Wed 28 OctEijsden 10:41Partial coverage0 min—
Tue 27 OctEijsden 10:42Partial coverage0 min—
Mon 26 OctEijsden 10:42No data—
Sun 25 OctMeerssen 10:19No data—
Sat 24 OctMeerssen 10:190 min—
Fri 23 OctEijsden 10:43No data—
Thu 22 OctEijsden 10:43Partial coverage0 min—
Wed 21 OctEijsden 10:43No data—
Tue 20 OctEijsden 10:42Partial coverage0 min—
Mon 19 OctEijsden 11:07Partial coverage0 min—
Sun 18 OctMeerssen 10:210 min—
Sat 17 OctMeerssen 10:21+1 min+1 min
Fri 16 OctEijsden 10:44No data—
Thu 15 OctEijsden 10:42No data—
Tue 13 OctEijsden 10:41Partial coverage0 min—
Mon 12 OctMeerssen 10:23No data—
Sun 11 OctMeerssen 10:210 min+1 min
Sat 10 OctMeerssen 10:22+1 min+1 min
Fri 9 OctEijsden 10:46Partial coverage+3 min+3 min
Thu 8 OctEijsden 10:42Partial coverage+18 min+18 min
Wed 7 OctMaastricht Randwyck 12:01+2 min+3 min
Tue 6 OctEijsden 10:41Partial coverage0 min—