Train Arriva 18934 Aachen Hbf – Liège-Guillemins

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

✓ Today’s run finished

Today, last fix heading to Eijsden at 13:39 0 min

  1. Aachen Hbf12:17
  2. Herzogenrath12:29
  3. Landgraaf12:38
  4. Meerssen13:05
  5. Eijsden13:26
  6. Vise13:32
  7. Liège-Guillemins13:50

Next service: tomorrow 12:17 from Aachen Hbf · Sun 8 Nov

Next departure 12:17 tomorrow · Aachen Hbf
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 4 full · 10 partial · 15 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 4 full · 14 partial · 70 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 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

  • Sat 24 Oct Max en route +6 min · last fix heading to Landgraaf +6 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 94% · 17
  • 3–10 min 6% · 1
  • 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
  • 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, 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
12:17on time on time
12:20 / 12:21— —
12:29 / 12:31— —
12:35— —
12:38 / 12:43— —
12:47 / 12:49— —
13:00— —
13:05— —
13:11 / 13:16— —
13:18 / 13:20— —
13:26 / 13:27— —
13:32 / 13:33— —
13:42 / 13:43— —
13:50— —

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