Train Arriva 32479 Roermond → Maastricht Randwyck
Arriva 32479 Roermond–Maastricht Randwyck: final delay under 3 min on 12 of its 13 runs with data in the last 30 days (92%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 23:27 (GMT+1).
An alert on this phone or computer when the 32479 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Maastricht at 22:34 0 min
- Roermond21:34
- Echt21:42
- Sittard21:52
- Geleen-Lutterade22:05
- Beek-Elsloo22:09
- Maastricht22:20
- Maastricht Randwyck22:25
Next service: tomorrow 21:34 from Roermond · Mon 23 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
- Tue 10 Nov Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 15
- 3–10 min 6% · 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=4
- 100% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 16 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 |
|---|---|---|---|
| 21:34 | on time | on time | |
| 21:42 | ≈ on time | ≈ on time | |
| 21:46 | ≈ on time | ≈ +1 min | |
| 21:52 / 22:01 | ≈ +1 min | ≈ +1 min | |
| 22:05 | ≈ +1 min | ≈ +2 min | |
| 22:09 | ≈ +1 min | ≈ +2 min | |
| 22:14 / 22:15 | ≈ +2 min | ≈ +2 min | |
| 22:20 / 22:22 | ≈ +2 min | ≈ +2 min | |
| 22:25 | +2 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Maastricht 22:34Partial coverage | 0 min | — |
| Sat 21 Nov | Maastricht 22:34Partial coverage | 0 min | — |
| Sun 15 Nov | Maastricht 22:38 | +2 min | +2 min |
| Sat 14 Nov | Maastricht 22:34 | +2 min | +2 min |
| Thu 12 Nov | — 22:28 | 0 min | — |
| Wed 11 Nov | — 22:27 | 0 min | — |
| Tue 10 Nov | — 22:29 | +4 min | +4 min |
| Sun 8 Nov | Maastricht 22:34Partial coverage | 0 min | — |
| Sat 7 Nov | Maastricht 22:34Partial coverage | 0 min | — |
| Fri 6 Nov | — 22:29 | 0 min | — |
| Wed 4 Nov | — 22:29 | +2 min | +2 min |
| Mon 2 Nov | — 22:29 | +2 min | +2 min |
| Sun 1 Nov | Maastricht 22:37Partial coverage | 0 min | — |
| Sat 31 Oct | Maastricht 22:36 | No data | — |
| Sun 25 Oct | Maastricht 22:36 | No data | — |
| Sat 24 Oct | Maastricht 22:36 | No data | — |
| Sun 18 Oct | Maastricht 22:39Partial coverage | +3 min | +3 min |
| Sat 17 Oct | Maastricht 22:36 | No data | — |
| Sun 11 Oct | Maastricht 22:36Partial coverage | 0 min | — |
| Sat 10 Oct | Geleen-Lutterade 22:19Partial coverage | 0 min | — |
| Sun 4 Oct | Maastricht 22:36 | No data | — |
| Sat 3 Oct | Bunde 22:50 | No data | — |
| Sun 27 Sept | Maastricht 22:40 | No data | — |
| Sat 26 Sept | Maastricht 22:36 | No data | — |
| Sun 20 Sept | Maastricht 22:36 | No data | — |
| Sat 19 Sept | Maastricht 22:36 | No data | — |
| Sun 13 Sept | Maastricht 22:36 | No data | — |
| Sat 12 Sept | Maastricht 22:36 | No data | — |
| Sun 6 Sept | Maastricht 22:36 | No data | — |
| Sat 5 Sept | Maastricht 22:36 | No data | — |