Train Arriva 32483 Roermond – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Friday 13 November +1 min

Next service: today 22:34 from Roermond · Sat 14 Nov

Next departure 22:34 today · Roermond
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 1 full · 5 partial · 5 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 1 full · 6 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 8 Nov Max en route +10 min · last fix heading to Maastricht +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 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
  • 100% F n=1
  • 100% S n=2
  • 75% S n=4

Stops and timetable

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

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