Train Arriva 32474 Maastricht Randwyck → Roermond
Arriva 32474 Maastricht Randwyck–Roermond: final delay under 3 min on 12 of its 12 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Roermond: 21:26. TrainsRadar data as of 22 Nov 2026, 20:30 (GMT+1).
An alert on this phone or computer when the 32474 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 20:30
Position estimated from the timetable
Heading to Roermond 0 min
Estimated arrival at Roermond 21:26
- Maastricht Randwyck20:35
- Maastricht20:38
- Beek-Elsloo20:52
- Geleen-Lutterade20:55
- Sittard21:01
- Echt21:17
- Roermond21:26
Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 12 runs arrived on time.
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
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 15
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- 100% W n=1
- 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, 15 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 | Today |
|---|---|---|---|---|
| 20:35 | on time | on time | ||
| 20:38 / 20:41 | ≈ on time | ≈ on time | ||
| 20:46 | ≈ on time | ≈ on time | ||
| 20:52 | ≈ on time | ≈ on time | ||
| 20:55 / 20:57 | ≈ on time | ≈ on time | ||
| 21:01 / 21:08 | ≈ on time | ≈ on time | ||
| 21:13 | ≈ on time | ≈ on time | ||
| 21:17 | ≈ on time | ≈ on time | ||
| 21:26 | on time | on time |
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 Randwyck 20:29Partial coverage | 0 min | — |
| Sat 21 Nov | Echt 21:29Partial coverage | 0 min | — |
| Sun 15 Nov | Geleen-Lutterade 21:09 | 0 min | — |
| Sat 14 Nov | Geleen-Lutterade 21:12 | 0 min | — |
| Thu 12 Nov | — 21:28 | 0 min | — |
| Tue 10 Nov | — 21:29 | 0 min | — |
| Sun 8 Nov | Echt 21:34Partial coverage | +1 min | +1 min |
| Sat 7 Nov | Echt 21:32Partial coverage | 0 min | — |
| Fri 6 Nov | — 21:29 | 0 min | — |
| Wed 4 Nov | — 21:29 | 0 min | — |
| Mon 2 Nov | — 21:29 | 0 min | — |
| Sun 1 Nov | Echt 21:33Partial coverage | 0 min | — |
| Sat 31 Oct | Echt 21:33 | No data | — |
| Sun 25 Oct | Echt 21:32 | No data | — |
| Sat 24 Oct | Echt 21:32 | No data | — |
| Sun 18 Oct | Echt 21:34Partial coverage | +2 min | +2 min |
| Sat 17 Oct | Echt 21:32 | No data | — |
| Sun 11 Oct | Echt 21:32Partial coverage | 0 min | — |
| Sat 10 Oct | Echt 21:31Partial coverage | 0 min | — |
| Sun 4 Oct | Echt 21:33 | No data | — |
| Sat 3 Oct | Echt 21:32 | No data | — |
| Sun 27 Sept | Echt 21:34 | No data | — |
| Sat 26 Sept | Echt 21:33 | No data | — |
| Sun 20 Sept | Echt 21:33 | No data | — |
| Sat 19 Sept | Echt 21:33 | No data | — |
| Sun 13 Sept | Echt 21:33 | No data | — |
| Sat 12 Sept | Echt 21:32 | No data | — |
| Sun 6 Sept | Geleen-Lutterade 21:11 | No data | — |
| Sat 5 Sept | Geleen-Lutterade 21:11 | No data | — |
| Sun 30 Aug | Echt 21:32 | No data | — |