Train Arriva 32263 Nijmegen – Roermond
It has not run yet today
Last recorded run: Saturday 7 November +2 min
Next service: today 17:38 from Nijmegen · Sun 8 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
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 18
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=2
- 100% W n=3
- 100% T n=1
- 100% F n=3
- 100% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 17:38 | on time | on time | |
| 17:41 | ≈ on time | ≈ on time | |
| 17:46 | ≈ on time | ≈ on time | |
| 17:50 / 17:52 | ≈ on time | ≈ on time | |
| 17:59 / 18:02 | ≈ on time | ≈ on time | |
| 18:07 / 18:08 | ≈ on time | ≈ on time | |
| 18:14 / 18:15 | ≈ on time | ≈ on time | |
| 18:28 | ≈ on time | ≈ on time | |
| 18:31 / 18:33 | ≈ on time | ≈ on time | |
| 18:38 | ≈ on time | ≈ on time | |
| 18:44 / 18:45 | ≈ on time | ≈ +1 min | |
| 18:50 | ≈ on time | ≈ +1 min | |
| 18:56 | 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 7 Nov | Swalmen 19:07Partial coverage | +2 min | +3 min |
| Fri 6 Nov | Reuver 18:59Partial coverage | +2 min | +3 min |
| Thu 5 Nov | Vierlingsbeek 18:22 | No data | — |
| Wed 4 Nov | Venray 18:29Partial coverage | 0 min | — |
| Tue 3 Nov | Vierlingsbeek 18:22 | No data | — |
| Mon 2 Nov | Vierlingsbeek 18:22 | No data | — |
| Sun 1 Nov | Swalmen 19:04 | +1 min | +1 min |
| Sat 31 Oct | Swalmen 19:05 | 0 min | — |
| Fri 30 Oct | Swalmen 19:04 | No data | — |
| Thu 29 Oct | Boxmeer 18:16 | No data | — |
| Wed 28 Oct | Vierlingsbeek 18:22Partial coverage | 0 min | — |
| Tue 27 Oct | Boxmeer 18:16 | No data | — |
| Mon 26 Oct | Vierlingsbeek 18:22Partial coverage | 0 min | — |
| Sun 25 Oct | Swalmen 19:04 | No data | — |
| Sat 24 Oct | Swalmen 19:05 | No data | — |
| Fri 23 Oct | Swalmen 19:04 | 0 min | +1 min |
| Thu 22 Oct | Reuver 18:59 | No data | — |
| Wed 21 Oct | Tegelen 18:52 | No data | — |
| Tue 20 Oct | Reuver 18:50 | 0 min | — |
| Mon 19 Oct | Tegelen 18:52 | No data | — |
| Sun 18 Oct | Swalmen 19:04 | 0 min | — |
| Sat 17 Oct | Swalmen 19:04 | No data | — |
| Fri 16 Oct | Swalmen 19:04 | No data | — |
| Thu 15 Oct | Blerick 18:42 | No data | — |
| Tue 13 Oct | Tegelen 18:50 | No data | — |
| Mon 12 Oct | Reuver 18:59Partial coverage | 0 min | — |
| Sun 11 Oct | Swalmen 19:05Partial coverage | 0 min | — |
| Sat 10 Oct | Swalmen 19:05Partial coverage | 0 min | +1 min |
| Fri 9 Oct | Venlo 18:47Partial coverage | +2 min | +2 min |
| Thu 8 Oct | Boxmeer 18:16Partial coverage | 0 min | — |