Train Arriva 32435 Roermond – Maastricht Randwyck
✓ Today’s run finished
Today, last fix heading to Maastricht at 11:34 No data
- Roermond10:34
- Echt10:42
- Sittard10:52
- Geleen-Lutterade11:05
- Beek-Elsloo11:09
- Maastricht11:20
- Maastricht Randwyck11:25
Next service: tomorrow 10: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 +10 min · last fix heading to Maastricht +10 min
- Fri 9 Oct Max en route +5 min · last fix heading to Maastricht +5 min
Distribution · 90 days
14 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 12
- 3–10 min 14% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 100% T n=3
- 67% W n=3
- 100% T n=1
- 0% F n=1
- 100% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 14 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 |
|---|---|---|---|
| 10:34 | on time | on time | |
| 10:42 | — | — | |
| 10:46 | — | — | |
| 10:52 / 11:01 | — | — | |
| 11:05 | — | — | |
| 11:09 | — | — | |
| 11:14 / 11:15 | — | — | |
| 11:20 / 11:22 | — | — | |
| 11: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 |
|---|---|---|---|
| Thu 5 Nov | Maastricht 11:34 | No data | — |
| Wed 4 Nov | Maastricht 11:44Partial coverage | +10 min | +10 min |
| Tue 3 Nov | Maastricht 11:35 | No data | — |
| Mon 2 Nov | Maastricht 11:34 | No data | — |
| Sun 1 Nov | Maastricht 11:37Partial coverage | 0 min | — |
| Sat 31 Oct | Maastricht 11:38Partial coverage | +2 min | +2 min |
| Fri 30 Oct | Bunde 11:29 | No data | — |
| Thu 29 Oct | Maastricht 11:36 | No data | — |
| Wed 28 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Tue 27 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Mon 26 Oct | Maastricht 11:36 | No data | — |
| Sun 25 Oct | Maastricht 11:36 | No data | — |
| Sat 24 Oct | Maastricht 11:37Partial coverage | +1 min | +1 min |
| Fri 23 Oct | Maastricht 11:36 | No data | — |
| Thu 22 Oct | Maastricht 11:37 | No data | — |
| Wed 21 Oct | Maastricht 11:36 | No data | — |
| Tue 20 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Mon 19 Oct | Maastricht 11:36 | No data | — |
| Sun 18 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Sat 17 Oct | Maastricht 11:36 | No data | — |
| Fri 16 Oct | Maastricht 11:36 | No data | — |
| Thu 15 Oct | Maastricht 11:36 | No data | — |
| Tue 13 Oct | Maastricht 11:37 | No data | — |
| Mon 12 Oct | Maastricht 11:36 | No data | — |
| Sun 11 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Sat 10 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Fri 9 Oct | Maastricht 11:41Partial coverage | +5 min | +5 min |
| Thu 8 Oct | Maastricht 11:36Partial coverage | 0 min | — |
| Wed 7 Oct | Maastricht 12:00Partial coverage | 0 min | — |
| Tue 6 Oct | Maastricht 11:36Partial coverage | 0 min | — |