Train Arriva 18926 Aachen Hbf – Liège-Guillemins

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

✓ Today’s run finished

Today, last fix heading to Eijsden at 11:44 No data

  1. Aachen Hbf10:17
  2. Herzogenrath10:29
  3. Landgraaf10:38
  4. Meerssen11:05
  5. Eijsden11:26
  6. Vise11:32
  7. Liège-Guillemins11:50

Next service: tomorrow 10:17 from Aachen Hbf · Sat 7 Nov

Next departure 10:17 tomorrow · Aachen Hbf
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 4 full · 11 partial · 14 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 4 full · 13 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

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