Train Arriva 18941 Liège-Guillemins – Aachen Hbf

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:08 from Liège-Guillemins · Fri 6 Nov

Next departure 13:08 today · Liège-Guillemins
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 4 full · 10 partial · 14 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 4 full · 13 partial · 70 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: +3 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 31 Oct Max en route +6 min · last fix heading to Eygelshoven Markt +6 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Eygelshoven Markt +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 33% S n=3
  • 100% S n=3

Stops and timetable

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

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