Train Arriva 32467 Roermond – Maastricht Randwyck

Roermond 18:34 → Maastricht Randwyck 19:25 Daily 0 h 51 min · 9 stops Arriva

It has not run yet today

Last recorded run: Saturday 7 November +3 min

Next service: today 18:34 from Roermond · Sun 8 Nov

Next departure 18:34 today · Roermond
On-time · 30 days
70%
7/10 runs under 3 min
RT coverage: 0 full · 10 partial · 9 no data
On-time · 90 days
73%
8/11 runs under 3 min
RT coverage: 0 full · 11 partial · 43 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Maastricht Randwyck, 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 31 Oct Max en route +4 min · last fix heading to Maastricht +4 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Maastricht +3 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Maastricht +3 min

Distribution · 90 days

11 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 73% · 8
  • 3–10 min 27% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 33% S n=3
  • 67% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 stops).

Last 90 days, 11 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
18:34on time on time
18:42— —
18:46— —
18:52 / 19:01— —
19:05— —
19:09— —
19:14 / 19:15— —
19:20 / 19:22— —
19:25— —

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 NovMaastricht 19:39Partial coverage+3 min+3 min
Fri 6 NovSusteren 18:59Partial coverage0 min—
Sun 1 NovMaastricht 19:39Partial coverage+3 min+3 min
Sat 31 OctMaastricht 19:40Partial coverage+4 min+4 min
Fri 30 OctSusteren 19:28No data—
Sun 25 OctMaastricht 19:36No data—
Sat 24 OctMaastricht 19:41No data—
Fri 23 OctMaastricht 19:36Partial coverage+2 min+3 min
Thu 22 OctEcht 18:56No data—
Wed 21 OctRoermond 18:48No data—
Tue 20 OctSusteren 18:50Partial coverage0 min—
Mon 19 OctEcht 18:56No data—
Sun 18 OctMaastricht 19:39Partial coverage+3 min+3 min
Sat 17 OctMaastricht 19:52No data—
Fri 16 OctMaastricht 19:36No data—
Tue 13 OctRoermond 18:48No data—
Mon 12 OctEcht 18:56Partial coverage0 min—
Sun 11 OctMaastricht 19:36Partial coverage0 min—
Sat 10 OctMaastricht 19:39Partial coverage+2 min+2 min
Fri 9 OctRoermond 18:48Partial coverage0 min—
Sun 4 OctMaastricht 19:36No data—
Sat 3 OctMaastricht 19:37No data—
Fri 2 OctSusteren 19:00No data—
Sun 27 SeptMaastricht 19:36No data—
Sat 26 SeptMaastricht 19:36No data—
Fri 25 SeptRoermond 18:48No data—
Sun 20 SeptMaastricht 19:36No data—
Sat 19 SeptMaastricht 19:36No data—
Fri 18 SeptSusteren 19:00No data—
Sun 13 SeptMaastricht 19:36No data—