Train Arriva 32264 Roermond – Nijmegen
It has not run yet today
Last recorded run: Saturday 14 November 0 min
Next service: today 18:04 from Roermond · Sun 15 Nov
Last 30 days
Arrival delay at Nijmegen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 13 Nov Max en route +11 min · last fix heading to Vierlingsbeek +11 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 95% · 21
- 3–10 min 0% · 0
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=2
- 100% W n=4
- 100% T n=1
- 67% F n=3
- 100% S n=4
- 100% S n=4
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 |
|---|---|---|---|
| 18:04 | on time | +1 min | |
| 18:09 | ≈ on time | ≈ +1 min | |
| 18:14 / 18:15 | ≈ on time | ≈ +1 min | |
| 18:21 | ≈ on time | ≈ +1 min | |
| 18:27 / 18:29 | ≈ on time | ≈ +1 min | |
| 18:31 | ≈ on time | ≈ +1 min | |
| 18:44 / 18:45 | ≈ on time | ≈ +1 min | |
| 18:50 / 18:51 | ≈ on time | ≈ +1 min | |
| 18:56 / 19:00 | ≈ on time | ≈ +1 min | |
| 19:07 / 19:08 | ≈ on time | ≈ +1 min | |
| 19:13 | ≈ on time | ≈ +1 min | |
| 19:18 | ≈ on time | ≈ +1 min | |
| 19:22 | 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 | Nijmegen Heyendaal 19:32Partial coverage | 0 min | — |
| Fri 13 Nov | Vierlingsbeek 19:04 | +11 min | +11 min |
| Thu 12 Nov | Tegelen 18:34 | 0 min | — |
| Wed 11 Nov | Swalmen 18:23 | 0 min | — |
| Tue 10 Nov | Tegelen 18:34 | 0 min | — |
| Mon 9 Nov | Swalmen 18:23 | 0 min | — |
| Sun 8 Nov | Nijmegen Heyendaal 19:33 | +1 min | — |
| Sat 7 Nov | Nijmegen Heyendaal 19:32Partial coverage | 0 min | — |
| Fri 6 Nov | Venray 18:59 | 0 min | — |
| Thu 5 Nov | Swalmen 18:23 | No data | — |
| Wed 4 Nov | Reuver 18:29 | 0 min | — |
| Tue 3 Nov | Swalmen 18:23 | No data | — |
| Mon 2 Nov | Swalmen 18:23 | No data | — |
| Sun 1 Nov | Tegelen 18:38 | +2 min | +3 min |
| Sat 31 Oct | Tegelen 18:36 | +1 min | — |
| Fri 30 Oct | Vierlingsbeek 19:05 | No data | — |
| Wed 28 Oct | Swalmen 18:23 | 0 min | — |
| Tue 27 Oct | Roermond 18:18 | No data | — |
| Mon 26 Oct | Swalmen 18:23 | 0 min | — |
| Sun 25 Oct | Tegelen 18:36 | No data | — |
| Sat 24 Oct | Tegelen 18:40 | No data | — |
| Fri 23 Oct | Tegelen 18:35 | No data | — |
| Thu 22 Oct | Tegelen 18:35 | No data | — |
| Wed 21 Oct | Tegelen 18:34 | No data | — |
| Tue 20 Oct | Tegelen 18:35 | 0 min | — |
| Mon 19 Oct | Tegelen 18:35 | No data | — |
| Sun 18 Oct | Tegelen 18:36 | +1 min | — |
| Sat 17 Oct | Tegelen 18:35 | No data | — |
| Fri 16 Oct | Nijmegen Heyendaal 19:32 | No data | — |
| Thu 15 Oct | Venlo 18:43 | No data | — |