Train Arriva 18938 Aachen Hbf – Liège-Guillemins

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

✓ Today’s run finished

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

  1. Aachen Hbf13:17
  2. Herzogenrath13:29
  3. Landgraaf13:38
  4. Meerssen14:05
  5. Eijsden14:26
  6. Vise14:32
  7. Liège-Guillemins14:50

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

Next departure 13:17 tomorrow · Aachen Hbf
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 4 full · 11 partial · 14 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 4 full · 15 partial · 69 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: 0 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

  • Thu 8 Oct Max en route +7 min · last fix heading to Eijsden +6 min
  • Sat 24 Oct Max en route +7 min · last fix heading to Valkenburg +6 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 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=3
  • 0% T n=1
  • 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
13:17on time on time
13:20 / 13:21— —
13:29 / 13:31— —
13:35— —
13:38 / 13:43— —
13:47 / 13:49— —
14:00— —
14:05— —
14:11 / 14:16— —
14:18 / 14:20— —
14:26 / 14:27— —
14:32 / 14:33— —
14:42 / 14:43— —
14: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 14:39Partial coverage0 min—
Fri 6 NovEijsden 14:43No data—
Thu 5 NovEijsden 14:39No data—
Wed 4 NovEijsden 14:42Partial coverage0 min—
Tue 3 NovEijsden 14:42No data—
Mon 2 NovEijsden 14:39Partial coverage0 min—
Sun 1 NovEijsden 14:42Partial coverage0 min—
Sat 31 OctEijsden 14:42Partial coverage0 min—
Fri 30 OctEijsden 14:43No data—
Thu 29 OctEijsden 14:55No data—
Wed 28 OctEijsden 14:42Partial coverage0 min—
Tue 27 OctEijsden 14:42Partial coverage0 min—
Mon 26 OctEijsden 14:42No data—
Sun 25 OctMeerssen 14:21No data—
Sat 24 OctValkenburg 14:14+6 min+7 min
Fri 23 OctEijsden 14:44No data—
Thu 22 OctEijsden 14:58No data—
Wed 21 OctEijsden 14:43No data—
Tue 20 OctEijsden 14:42Partial coverage0 min—
Mon 19 OctEijsden 14:49Partial coverage0 min—
Sun 18 OctMeerssen 14:210 min—
Sat 17 OctMeerssen 14:19No data—
Fri 16 OctEijsden 14:43No data—
Thu 15 OctEijsden 14:42No data—
Tue 13 OctEijsden 14:42Partial coverage0 min—
Mon 12 OctMeerssen 14:21No data—
Sun 11 OctMeerssen 14:21+1 min+1 min
Sat 10 OctMeerssen 14:200 min—
Fri 9 OctEijsden 14:43Partial coverage0 min+3 min
Thu 8 OctEijsden 14:49Partial coverage+6 min+7 min