Train Arriva 32256 Roermond – Nijmegen
✓ Today’s run finished
Today, last fix heading to Nijmegen Heyendaal at 17:32 No data
- Roermond16:04
- Reuver16:14
- Venlo16:27
- Venray16:44
- Boxmeer16:56
- Nijmegen Heyendaal17:18
- Nijmegen17:22
Next service: tomorrow 16:04 from Roermond · Fri 6 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
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 100% · 16
- 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=3
- 100% W n=3
- 100% T n=1
- 100% F n=1
- 100% S n=3
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 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 |
|---|---|---|---|
| 16:04 | on time | on time | |
| 16:09 | ≈ on time | ≈ +1 min | |
| 16:14 / 16:15 | ≈ on time | ≈ +1 min | |
| 16:21 | ≈ on time | ≈ +1 min | |
| 16:27 / 16:29 | ≈ on time | ≈ +1 min | |
| 16:31 | ≈ on time | ≈ +1 min | |
| 16:44 / 16:45 | ≈ +1 min | ≈ +1 min | |
| 16:50 / 16:51 | ≈ +1 min | ≈ +1 min | |
| 16:56 / 17:00 | ≈ +1 min | ≈ +1 min | |
| 17:07 / 17:08 | ≈ +1 min | ≈ +1 min | |
| 17:12 | ≈ +1 min | ≈ +1 min | |
| 17:18 | ≈ +1 min | ≈ +2 min | |
| 17:22 | +1 min | +2 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 |
|---|---|---|---|
| Thu 5 Nov | Nijmegen Heyendaal 17:32 | No data | — |
| Wed 4 Nov | Nijmegen Heyendaal 17:32Partial coverage | 0 min | — |
| Tue 3 Nov | Nijmegen Heyendaal 17:32 | No data | — |
| Mon 2 Nov | Nijmegen Heyendaal 17:32 | No data | — |
| Sun 1 Nov | Tegelen 16:38 | +2 min | +3 min |
| Sat 31 Oct | Tegelen 16:37 | +1 min | +1 min |
| Fri 30 Oct | Nijmegen Heyendaal 17:32 | No data | — |
| Thu 29 Oct | Nijmegen Heyendaal 17:32 | No data | — |
| Wed 28 Oct | Nijmegen Heyendaal 17:32Partial coverage | 0 min | — |
| Tue 27 Oct | Nijmegen Heyendaal 17:32Partial coverage | 0 min | — |
| Mon 26 Oct | Nijmegen Heyendaal 17:32 | No data | — |
| Sun 25 Oct | Tegelen 16:38 | No data | — |
| Sat 24 Oct | Tegelen 16:36 | +1 min | +1 min |
| Fri 23 Oct | Tegelen 16:36 | No data | — |
| Thu 22 Oct | Tegelen 16:37 | No data | — |
| Wed 21 Oct | Tegelen 16:36 | No data | — |
| Tue 20 Oct | Tegelen 16:36 | 0 min | — |
| Mon 19 Oct | Tegelen 16:37 | 0 min | — |
| Sun 18 Oct | Tegelen 16:35 | No data | — |
| Sat 17 Oct | Tegelen 16:37 | No data | — |
| Fri 16 Oct | Nijmegen Heyendaal 17:32 | No data | — |
| Thu 15 Oct | Nijmegen Heyendaal 17:32 | No data | — |
| Tue 13 Oct | Nijmegen Heyendaal 17:32 | No data | — |
| Mon 12 Oct | Nijmegen Heyendaal 17:33Partial coverage | 0 min | — |
| Sun 11 Oct | Nijmegen Heyendaal 17:33Partial coverage | +1 min | — |
| Sat 10 Oct | Nijmegen Heyendaal 17:32Partial coverage | 0 min | — |
| Fri 9 Oct | Nijmegen Heyendaal 17:32Partial coverage | 0 min | — |
| Thu 8 Oct | Nijmegen Heyendaal 17:33 | +1 min | +1 min |
| Wed 7 Oct | Nijmegen Heyendaal 17:32Partial coverage | +1 min | — |
| Tue 6 Oct | Nijmegen Heyendaal 17:32Partial coverage | +1 min | — |