Train Arriva 32253 Nijmegen – Roermond
It has not run yet today
Last recorded run: Saturday 14 November 0 min
Next service: today 15:08 from Nijmegen · Sun 15 Nov
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
Worst days
- Wed 11 Nov Max en route +7 min · last fix heading to Swalmen +7 min
- Tue 10 Nov Max en route +5 min · last fix heading to Swalmen +4 min
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 20
- 3–10 min 9% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 67% T n=3
- 75% W n=4
- 100% T n=3
- 100% F n=2
- 100% S n=4
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 22 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 |
|---|---|---|---|
| 15:08 | on time | on time | |
| 15:11 | ≈ on time | ≈ on time | |
| 15:16 | ≈ on time | ≈ on time | |
| 15:20 / 15:22 | ≈ on time | ≈ on time | |
| 15:29 / 15:32 | ≈ on time | ≈ on time | |
| 15:37 / 15:38 | ≈ on time | ≈ on time | |
| 15:44 / 15:45 | ≈ on time | ≈ on time | |
| 15:58 | ≈ on time | ≈ on time | |
| 16:00 / 16:03 | ≈ on time | ≈ on time | |
| 16:08 | ≈ on time | ≈ +1 min | |
| 16:14 / 16:15 | ≈ on time | ≈ +1 min | |
| 16:20 | ≈ on time | ≈ +1 min | |
| 16:26 | on time | +1 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 |
|---|---|---|---|
| Sat 14 Nov | Swalmen 16:34Partial coverage | 0 min | — |
| Fri 13 Nov | Swalmen 16:34Partial coverage | 0 min | — |
| Thu 12 Nov | Swalmen 16:34Partial coverage | 0 min | +1 min |
| Wed 11 Nov | Swalmen 16:39Partial coverage | +7 min | +7 min |
| Tue 10 Nov | Swalmen 16:39Partial coverage | +4 min | +5 min |
| Mon 9 Nov | Swalmen 16:34 | 0 min | — |
| Sun 8 Nov | Swalmen 16:35 | +1 min | — |
| Sat 7 Nov | Swalmen 16:34 | 0 min | +1 min |
| Fri 6 Nov | Swalmen 16:34 | No data | — |
| Thu 5 Nov | Swalmen 16:44 | No data | — |
| Wed 4 Nov | Swalmen 16:34 | 0 min | — |
| Tue 3 Nov | Swalmen 16:34 | No data | — |
| Mon 2 Nov | Swalmen 16:39 | No data | — |
| Sun 1 Nov | Swalmen 16:34 | No data | — |
| Sat 31 Oct | Swalmen 16:34 | No data | — |
| Fri 30 Oct | Swalmen 16:34 | No data | — |
| Thu 29 Oct | Swalmen 16:34 | 0 min | — |
| Wed 28 Oct | Swalmen 16:38 | 0 min | — |
| Tue 27 Oct | Swalmen 16:40 | No data | — |
| Mon 26 Oct | Swalmen 16:36 | No data | — |
| Sun 25 Oct | Swalmen 16:36 | No data | — |
| Sat 24 Oct | Swalmen 16:35 | 0 min | — |
| Fri 23 Oct | Swalmen 16:34 | No data | — |
| Thu 22 Oct | Swalmen 16:36 | No data | — |
| Wed 21 Oct | Swalmen 16:35 | No data | — |
| Tue 20 Oct | Swalmen 16:35 | 0 min | — |
| Mon 19 Oct | Swalmen 16:35 | 0 min | — |
| Sun 18 Oct | Swalmen 16:34 | No data | — |
| Sat 17 Oct | Swalmen 16:35 | No data | — |
| Fri 16 Oct | Swalmen 17:01 | No data | — |