Train Arriva 18937 Liège-Guillemins – Aachen Hbf

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

✓ Today’s run finished

Today, last fix heading to Eygelshoven Markt at 13:42 0 min

  1. Liège-Guillemins12:08
  2. Vise12:26
  3. Maastricht Randwyck12:37
  4. Valkenburg13:03
  5. Eygelshoven Markt13:25
  6. Herzogenrath13:29
  7. Aachen Hbf13:42

Next service: tomorrow 12:08 from Liège-Guillemins · Sun 8 Nov

Next departure 12:08 tomorrow · Liège-Guillemins
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 4 full · 11 partial · 13 no data
On-time · 90 days
95%
18/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: +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

  • Sat 24 Oct Max en route +5 min · last fix heading to Eygelshoven Markt +5 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 95% · 18
  • 3–10 min 5% · 1
  • 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=2
  • 100% F n=1
  • 75% 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
12:08on time on time
12:16 / 12:17— —
12:26 / 12:27— —
12:30— —
12:37 / 12:42— —
12:45 / 12:53— —
12:58— —
13:03— —
13:15 / 13:18— —
13:22— —
13:25— —
13:29 / 13:30— —
13:37 / 13:38— —
13: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
Sat 7 NovEygelshoven Markt 13:42Partial coverage0 min—
Fri 6 NovEygelshoven Markt 13:42No data—
Thu 5 NovEygelshoven Markt 13:44No data—
Wed 4 NovEygelshoven Markt 13:42Partial coverage0 min—
Tue 3 NovEygelshoven Markt 13:42No data—
Mon 2 NovEygelshoven Markt 13:43No data—
Sun 1 NovEygelshoven Markt 13:44Partial coverage0 min—
Sat 31 OctEygelshoven Markt 13:46Partial coverage+3 min+8 min
Fri 30 OctEygelshoven Markt 13:43No data—
Thu 29 OctEygelshoven Markt 13:57Partial coverage0 min—
Wed 28 OctEygelshoven Markt 13:42Partial coverage0 min—
Tue 27 OctEygelshoven Markt 13:44Partial coverage0 min—
Mon 26 OctEygelshoven Markt 13:42No data—
Sun 25 OctEygelshoven Markt 13:42No data—
Sat 24 OctEygelshoven Markt 13:48+5 min+5 min
Fri 23 OctEygelshoven Markt 13:44No data—
Thu 22 OctEygelshoven Markt 13:51No data—
Wed 21 OctEygelshoven Markt 13:43No data—
Tue 20 OctEygelshoven Markt 13:42Partial coverage0 min—
Mon 19 OctEygelshoven Markt 13:43Partial coverage0 min—
Sun 18 OctEygelshoven Markt 13:43+1 min—
Sat 17 OctEygelshoven Markt 13:45No data—
Fri 16 OctEygelshoven Markt 13:42No data—
Thu 15 OctEygelshoven Markt 13:42No data—
Tue 13 OctEygelshoven Markt 13:39Partial coverage0 min—
Sun 11 OctEygelshoven Markt 13:420 min—
Sat 10 OctEygelshoven Markt 13:430 min—
Fri 9 OctEygelshoven Markt 13:43Partial coverage+1 min—
Thu 8 OctEygelshoven Markt 13:43Partial coverage0 min—
Wed 7 OctEygelshoven Markt 13:42Partial coverage0 min—