Train Arriva 32475 Roermond – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

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

Next departure 20:34 today · Roermond
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 6 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 25 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: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 5 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
20:34on time on time
20:42— —
20:46— —
20:52 / 21:01— —
21:05— —
21:09— —
21:14 / 21:15— —
21:20 / 21:22— —
21: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 21:34Partial coverage0 min—
Tue 3 Nov— 21:27No data—
Sun 1 NovMaastricht 21:34Partial coverage0 min—
Sat 31 OctMaastricht 21:37No data—
Fri 30 Oct— 21:28No data—
Sun 25 OctMaastricht 21:38No data—
Sat 24 OctMaastricht 21:36No data—
Sun 18 OctMaastricht 21:36Partial coverage0 min—
Sat 17 OctMaastricht 21:36No data—
Sun 11 OctMaastricht 21:37Partial coverage+1 min+2 min
Sat 10 OctMaastricht 21:36Partial coverage+1 min—
Sun 4 OctMaastricht 21:36No data—
Sat 3 OctMaastricht 21:45No data—
Sun 27 SeptMaastricht 21:36No data—
Sat 26 SeptMaastricht 21:37No data—
Sun 20 SeptMaastricht 21:36No data—
Sat 19 SeptMaastricht 21:36No data—
Sun 13 SeptMaastricht 21:38No data—
Sat 12 SeptMaastricht 21:37No data—
Sun 6 SeptMaastricht 21:36No data—
Sat 5 SeptMaastricht 21:36No data—
Sun 30 AugMaastricht 21:37No data—
Sat 29 AugMaastricht 21:37No data—
Sun 23 AugMaastricht 21:37No data—
Sat 22 AugMaastricht 21:36No data—
Fri 21 AugRoermond 20:48No data—
Sun 16 AugMaastricht 21:40No data—
Sat 15 AugMaastricht 21:36No data—
Fri 14 AugSusteren 21:00No data—
Wed 12 AugRoermond 20:48No data—