Train Arriva 32416 Maastricht Randwyck – Roermond

Maastricht Randwyck 06:05 → Roermond 06:56 Mon, Tue, Wed, Thu, Fri, Sat 0 h 51 min · 9 stops Arriva

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 06:05 from Maastricht Randwyck · Mon 9 Nov

Next departure 06:05 tomorrow · Maastricht Randwyck
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 0 full · 21 partial · 3 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 0 full · 24 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Roermond, 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 3 Nov Max en route +12 min · last fix heading to Echt +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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:05on time on time
06:08 / 06:11— —
06:16— —
06:22— —
06:25 / 06:27— —
06:31 / 06:38— —
06:43— —
06:47— —
06:56— —

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 NovEcht 07:03Partial coverage0 min—
Fri 6 NovEcht 07:03No data—
Thu 5 NovEcht 07:03No data—
Wed 4 NovEcht 07:02Partial coverage0 min—
Tue 3 NovEcht 07:08Partial coverage+12 min+12 min
Mon 2 NovEcht 07:03No data—
Sat 31 OctEcht 07:04Partial coverage+2 min+2 min
Fri 30 OctEcht 07:03Partial coverage0 min—
Thu 29 OctEcht 07:03Partial coverage0 min—
Wed 28 OctEcht 07:03Partial coverage0 min—
Tue 27 OctEcht 07:03Partial coverage+1 min+1 min
Mon 26 OctEcht 07:03Partial coverage+1 min+1 min
Sat 24 OctEcht 07:03Partial coverage0 min+1 min
Fri 23 OctEcht 07:02Partial coverage0 min—
Thu 22 OctEcht 07:02Partial coverage0 min+6 min
Wed 21 OctEcht 07:03Partial coverage0 min—
Tue 20 OctEcht 07:03Partial coverage0 min—
Mon 19 OctEcht 07:03Partial coverage0 min—
Sat 17 OctEcht 07:04Partial coverage+2 min+2 min
Fri 16 OctEcht 07:02Partial coverage+2 min+2 min
Thu 15 OctEcht 07:04Partial coverage+1 min+1 min
Tue 13 OctEcht 07:03Partial coverage0 min—
Mon 12 OctEcht 07:04Partial coverage0 min—
Sat 10 OctEcht 07:03Partial coverage0 min—
Fri 9 OctEcht 07:03Partial coverage0 min—
Thu 8 OctEcht 07:03Partial coverage0 min—
Wed 7 OctEcht 07:03Partial coverage+1 min+1 min
Tue 6 OctEcht 07:02No data—
Mon 5 OctEcht 07:03No data—
Sat 3 OctEcht 07:03No data—