Train Arriva 32471 Roermond – Maastricht Randwyck
It has not run yet today
Last recorded run: Wednesday 4 November +4 min
Next service: today 19:34 from Roermond · Fri 6 Nov
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
- Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 5
- 3–10 min 17% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- 0% W n=1
- — 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, 6 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 19:34 | on time | on time | |
| 19:42 | — | — | |
| 19:46 | — | — | |
| 19:52 / 20:01 | — | — | |
| 20:05 | — | — | |
| 20:09 | — | — | |
| 20:14 / 20:15 | — | — | |
| 20:20 / 20:22 | — | — | |
| 20: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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | — 20:29 | +4 min | +4 min |
| Mon 2 Nov | — 20:27 | No data | — |
| Sun 1 Nov | Maastricht 20:38Partial coverage | +2 min | +2 min |
| Sat 31 Oct | Maastricht 20:36Partial coverage | 0 min | — |
| Sun 25 Oct | Maastricht 20:39 | No data | — |
| Sat 24 Oct | Maastricht 20:37 | No data | — |
| Sun 18 Oct | Maastricht 20:36Partial coverage | 0 min | — |
| Sat 17 Oct | Maastricht 20:36 | No data | — |
| Fri 16 Oct | Susteren 20:00 | No data | — |
| Tue 13 Oct | — 20:58 | No data | — |
| Sun 11 Oct | Maastricht 20:37Partial coverage | +1 min | +2 min |
| Sat 10 Oct | Maastricht 20:36Partial coverage | 0 min | — |
| Sun 4 Oct | Maastricht 20:36 | No data | — |
| Sat 3 Oct | Maastricht 20:39 | No data | — |
| Sun 27 Sept | Maastricht 20:38 | No data | — |
| Sat 26 Sept | Maastricht 20:36 | No data | — |
| Sun 20 Sept | Maastricht 20:36 | No data | — |
| Sat 19 Sept | Maastricht 20:36 | No data | — |
| Sun 13 Sept | Maastricht 20:36 | No data | — |
| Sat 12 Sept | Maastricht 20:36 | No data | — |
| Sun 6 Sept | Maastricht 20:37 | No data | — |
| Sat 5 Sept | Maastricht 20:37 | No data | — |
| Sun 30 Aug | Maastricht 20:36 | No data | — |
| Sat 29 Aug | Maastricht 20:36 | No data | — |
| Sun 23 Aug | Maastricht 20:36 | No data | — |
| Sat 22 Aug | Maastricht 20:36 | No data | — |
| Fri 21 Aug | Maastricht 20:36 | No data | — |
| Mon 17 Aug | Echt 19:56 | No data | — |
| Sun 16 Aug | Maastricht 20:36 | No data | — |
| Sat 15 Aug | Maastricht 20:37 | No data | — |