Train Arriva 32479 Roermond – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

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

Next departure 21:34 today · Roermond
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 6 full · 4 partial · 4 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 6 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: +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

  • Tue 10 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 0% T n=1
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 12 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
21:34on time on time
21:42≈ on time ≈ on time
21:46≈ on time ≈ +1 min
21:52 / 22:01≈ on time ≈ +1 min
22:05≈ +1 min ≈ +2 min
22:09≈ +1 min ≈ +2 min
22:14 / 22:15≈ +1 min ≈ +2 min
22:20 / 22:22≈ +1 min ≈ +3 min
22:25+1 min +3 min

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 12 Nov— 22:280 min—
Wed 11 Nov— 22:270 min—
Tue 10 Nov— 22:29+4 min+4 min
Sun 8 NovMaastricht 22:34Partial coverage0 min—
Sat 7 NovMaastricht 22:34Partial coverage0 min—
Fri 6 Nov— 22:290 min—
Wed 4 Nov— 22:29+2 min+2 min
Mon 2 Nov— 22:29+2 min+2 min
Sun 1 NovMaastricht 22:37Partial coverage0 min—
Sat 31 OctMaastricht 22:36No data—
Sun 25 OctMaastricht 22:36No data—
Sat 24 OctMaastricht 22:36No data—
Sun 18 OctMaastricht 22:39Partial coverage+3 min+3 min
Sat 17 OctMaastricht 22:36No data—
Sun 11 OctMaastricht 22:36Partial coverage0 min—
Sat 10 OctGeleen-Lutterade 22:19Partial coverage0 min—
Sun 4 OctMaastricht 22:36No data—
Sat 3 OctBunde 22:50No data—
Sun 27 SeptMaastricht 22:40No data—
Sat 26 SeptMaastricht 22:36No data—
Sun 20 SeptMaastricht 22:36No data—
Sat 19 SeptMaastricht 22:36No data—
Sun 13 SeptMaastricht 22:36No data—
Sat 12 SeptMaastricht 22:36No data—
Sun 6 SeptMaastricht 22:36No data—
Sat 5 SeptMaastricht 22:36No data—
Sun 30 AugMaastricht 22:36No data—
Sat 29 AugMaastricht 22:35No data—
Sun 23 AugMaastricht 22:36No data—
Sat 22 AugMaastricht 22:36No data—