Train Arriva 18929 Liège-Guillemins – Aachen Hbf

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

✓ Today’s run finished

Today, last fix heading to Eygelshoven Markt at 11:43 0 min

  1. Liège-Guillemins10:08
  2. Vise10:26
  3. Maastricht Randwyck10:37
  4. Valkenburg11:03
  5. Eygelshoven Markt11:25
  6. Herzogenrath11:29
  7. Aachen Hbf11:42

Next service: tomorrow 10:08 from Liège-Guillemins · Mon 9 Nov

Next departure 10:08 tomorrow · Liège-Guillemins
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 4 full · 11 partial · 13 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 4 full · 15 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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