Train Arriva 32321 Nijmegen – Venray
It does not run today
Last recorded run: Friday 13 November 0 min
Next service: tomorrow 07:23 from Nijmegen · Mon 16 Nov
Last 30 days
Arrival delay at Venray, 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
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 13
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=4
- 100% W n=2
- 100% T n=2
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 07:23 | on time | +1 min | |
| 07:26 | — | — | |
| 07:32 | — | — | |
| 07:36 / 07:37 | — | — | |
| 07:45 | — | — | |
| 07:51 | — | — | |
| 07:58 | — | — |
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 |
|---|---|---|---|
| Fri 13 Nov | Vierlingsbeek 08:04Partial coverage | 0 min | — |
| Thu 12 Nov | Vierlingsbeek 08:04Partial coverage | 0 min | — |
| Wed 11 Nov | Vierlingsbeek 08:04Partial coverage | 0 min | — |
| Tue 10 Nov | Vierlingsbeek 08:07Partial coverage | +1 min | +1 min |
| Mon 9 Nov | Vierlingsbeek 08:04Partial coverage | 0 min | — |
| Fri 6 Nov | Vierlingsbeek 08:07 | No data | — |
| Thu 5 Nov | Vierlingsbeek 08:08 | No data | — |
| Wed 4 Nov | Vierlingsbeek 08:04 | No data | — |
| Tue 3 Nov | Vierlingsbeek 08:07Partial coverage | 0 min | — |
| Mon 2 Nov | Cuijk 07:49Partial coverage | 0 min | — |
| Fri 30 Oct | Vierlingsbeek 08:07Partial coverage | 0 min | — |
| Thu 29 Oct | Cuijk 07:51Partial coverage | No data | — |
| Wed 28 Oct | Vierlingsbeek 08:05Partial coverage | No data | — |
| Tue 27 Oct | Vierlingsbeek 08:07Partial coverage | 0 min | — |
| Mon 26 Oct | Vierlingsbeek 08:05 | No data | — |
| Thu 15 Oct | Vierlingsbeek 08:08 | No data | — |
| Mon 12 Oct | Vierlingsbeek 08:06 | No data | — |
| Fri 9 Oct | Vierlingsbeek 08:05Partial coverage | 0 min | — |
| Thu 8 Oct | Vierlingsbeek 08:07Partial coverage | +2 min | +2 min |
| Wed 7 Oct | Vierlingsbeek 08:07Partial coverage | +1 min | +1 min |
| Tue 6 Oct | Vierlingsbeek 08:06Partial coverage | 0 min | — |
| Mon 5 Oct | Vierlingsbeek 08:08 | No data | — |
| Fri 2 Oct | Vierlingsbeek 08:12 | No data | — |
| Thu 1 Oct | Vierlingsbeek 08:06 | No data | — |
| Wed 30 Sept | Vierlingsbeek 08:06 | No data | — |
| Tue 29 Sept | Vierlingsbeek 08:07 | No data | — |
| Mon 28 Sept | Vierlingsbeek 08:07 | No data | — |
| Fri 25 Sept | Vierlingsbeek 08:06 | No data | — |
| Thu 24 Sept | Cuijk 07:51 | No data | — |
| Wed 23 Sept | Vierlingsbeek 08:05 | No data | — |