Train Arriva 18925 Liège-Guillemins – Aachen Hbf

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

It has not run yet today

Last recorded run: Saturday 7 November +1 min

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

Next departure 09:08 today · Liège-Guillemins
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 5 full · 9 partial · 13 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 6 full · 12 partial · 68 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: +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

  • Thu 8 Oct Max en route +5 min · last fix heading to Eygelshoven Markt +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Eygelshoven Markt +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=4
  • 67% W n=3
  • 0% T n=1
  • 100% F n=1
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 18 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:08on time on time
09:16 / 09:17≈ on time ≈ on time
09:26 / 09:27≈ on time ≈ on time
09:30≈ on time ≈ on time
09:37 / 09:42≈ on time ≈ on time
09:45 / 09:53≈ on time ≈ +1 min
09:58≈ on time ≈ +1 min
10:03≈ on time ≈ +1 min
10:15 / 10:18≈ on time ≈ +1 min
10:22≈ on time ≈ +1 min
10:25≈ on time ≈ +1 min
10:29 / 10:30≈ on time ≈ +1 min
10:37 / 10:38≈ on time ≈ +1 min
10:42on time +1 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
Sat 7 NovEygelshoven Markt 10:44Partial coverage+1 min—
Fri 6 NovEygelshoven Markt 10:44No data—
Thu 5 NovEygelshoven Markt 10:39No data—
Wed 4 NovEygelshoven Markt 10:44Partial coverage+3 min+4 min
Tue 3 NovEygelshoven Markt 10:42No data—
Mon 2 NovEygelshoven Markt 10:42No data—
Sun 1 NovEygelshoven Markt 10:42Partial coverage0 min—
Sat 31 OctEygelshoven Markt 10:42Partial coverage0 min—
Fri 30 OctEygelshoven Markt 10:43No data—
Thu 29 OctEygelshoven Markt 10:44No data—
Wed 28 OctEygelshoven Markt 10:42Partial coverage0 min—
Tue 27 OctEygelshoven Markt 10:44Partial coverage0 min—
Mon 26 OctEygelshoven Markt 10:42No data—
Sun 25 OctEygelshoven Markt 10:45No data—
Sat 24 OctEygelshoven Markt 10:45+2 min+2 min
Fri 23 OctEygelshoven Markt 10:45No data—
Thu 22 OctEygelshoven Markt 10:43No data—
Wed 21 OctEygelshoven Markt 10:43No data—
Tue 20 OctEygelshoven Markt 10:43Partial coverage0 min—
Mon 19 OctEygelshoven Markt 10:43Partial coverage0 min—
Sun 18 OctEygelshoven Markt 10:420 min—
Sat 17 OctEygelshoven Markt 10:440 min—
Fri 16 OctEygelshoven Markt 10:42No data—
Thu 15 OctEygelshoven Markt 10:42No data—
Tue 13 OctEygelshoven Markt 10:42Partial coverage0 min—
Sun 11 OctEygelshoven Markt 10:430 min—
Sat 10 OctEygelshoven Markt 10:420 min—
Fri 9 OctEygelshoven Markt 10:43Partial coverage0 min—
Thu 8 OctEygelshoven Markt 10:47Partial coverage+5 min+5 min
Wed 7 OctEygelshoven Markt 12:030 min—