Train Arriva 18906 Maastricht – Liège-Guillemins

Maastricht 06:16 → Liège-Guillemins 06:50 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 6 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 06:16 from Maastricht · Fri 6 Nov

Next departure 06:16 today · Maastricht
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 2 full · 15 partial · 3 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 2 full · 17 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 6 Oct Max en route +59 min · last fix heading to Eijsden +59 min
  • Thu 8 Oct Max en route +10 min · last fix heading to Eijsden +10 min
  • Tue 13 Oct Max en route +7 min · last fix heading to Eijsden +7 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 84% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

  • 100% M n=2
  • 60% T n=5
  • 100% W n=4
  • 75% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
06:16on time on time
06:18 / 06:20— —
06:26 / 06:27— —
06:32 / 06:33— —
06:42 / 06:43— —
06: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
Thu 5 NovEijsden 06:42No data—
Wed 4 NovEijsden 06:39Partial coverage0 min—
Tue 3 NovEijsden 06:43Partial coverage0 min—
Mon 2 NovEijsden 06:42No data—
Fri 30 OctEijsden 06:42Partial coverage0 min—
Thu 29 OctEijsden 06:41Partial coverage0 min—
Wed 28 OctEijsden 06:43Partial coverage0 min—
Tue 27 OctEijsden 06:41Partial coverage0 min—
Mon 26 OctEijsden 06:410 min—
Fri 23 OctEijsden 06:41Partial coverage0 min—
Thu 22 OctEijsden 06:42Partial coverage0 min—
Wed 21 OctEijsden 06:44Partial coverage+1 min+1 min
Tue 20 OctEijsden 06:42Partial coverage0 min—
Mon 19 OctEijsden 06:410 min—
Fri 16 OctEijsden 06:43Partial coverage0 min—
Thu 15 OctEijsden 06:42Partial coverage0 min—
Tue 13 OctEijsden 06:50Partial coverage+7 min+7 min
Mon 12 OctEijsden 06:41No data—
Fri 9 OctEijsden 06:41Partial coverage0 min—
Thu 8 OctEijsden 06:52Partial coverage+10 min+10 min
Wed 7 OctEijsden 06:41Partial coverage0 min—
Tue 6 OctEijsden 07:49Partial coverage+59 min+59 min
Mon 5 OctEijsden 07:15No data—
Fri 2 OctEijsden 06:42No data—
Thu 1 OctEijsden 06:53No data—
Wed 30 SeptEijsden 06:41No data—
Tue 29 SeptEijsden 06:41No data—
Mon 28 SeptEijsden 07:06No data—
Fri 25 SeptEijsden 06:42No data—
Thu 24 SeptEijsden 06:41No data—