Train Arriva 32327 Nijmegen – Venray
✓ Today’s run finished
Today, last fix heading to Vierlingsbeek at 09:34 No data
- Nijmegen08:53
- Nijmegen Heyendaal08:56
- Mook-Molenhoek09:02
- Cuijk09:06
- Boxmeer09:15
- Vierlingsbeek09:21
- Venray09:28
Next service: tomorrow 08:53 from Nijmegen · Wed 4 Nov
Next departure 08:53 tomorrow · Nijmegen
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 7 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 35 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min
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
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 6
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 100% T n=2
- 100% W n=2
- 100% T n=1
- 100% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
| Stop | Sched. |
|---|---|
| 08:53 | |
| 08:56 | |
| 09:02 | |
| 09:06 / 09:07 | |
| 09:15 | |
| 09:21 | |
| 09:28 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 3 Nov | Vierlingsbeek 09:34 | No data | — |
| Fri 30 Oct | Vierlingsbeek 09:35 | No data | — |
| Wed 28 Oct | Vierlingsbeek 09:36Partial coverage | 0 min | — |
| Tue 27 Oct | Vierlingsbeek 09:37Partial coverage | 0 min | — |
| Mon 26 Oct | Vierlingsbeek 09:36 | No data | — |
| Fri 16 Oct | Mook-Molenhoek 09:16 | No data | — |
| Thu 15 Oct | Vierlingsbeek 09:36 | No data | — |
| Mon 12 Oct | Vierlingsbeek 09:38 | No data | — |
| Fri 9 Oct | Vierlingsbeek 09:39Partial coverage | +2 min | +3 min |
| Thu 8 Oct | Vierlingsbeek 09:37Partial coverage | +1 min | +1 min |
| Wed 7 Oct | Vierlingsbeek 09:35Partial coverage | 0 min | — |
| Tue 6 Oct | Vierlingsbeek 09:38Partial coverage | +3 min | +3 min |
| Mon 5 Oct | Vierlingsbeek 09:38 | No data | — |
| Fri 2 Oct | Vierlingsbeek 09:37 | No data | — |
| Thu 1 Oct | Vierlingsbeek 09:35 | No data | — |
| Wed 30 Sept | Vierlingsbeek 09:36 | No data | — |
| Tue 29 Sept | Vierlingsbeek 09:37 | No data | — |
| Mon 28 Sept | Vierlingsbeek 09:37 | No data | — |
| Fri 25 Sept | Vierlingsbeek 09:36 | No data | — |
| Thu 24 Sept | Vierlingsbeek 09:38 | No data | — |
| Wed 23 Sept | Vierlingsbeek 09:36 | No data | — |
| Tue 22 Sept | Vierlingsbeek 09:35 | No data | — |
| Mon 21 Sept | Vierlingsbeek 09:35 | No data | — |
| Fri 18 Sept | Vierlingsbeek 09:39 | No data | — |
| Thu 17 Sept | Vierlingsbeek 09:37 | No data | — |
| Wed 16 Sept | Vierlingsbeek 09:38 | No data | — |
| Tue 15 Sept | Vierlingsbeek 09:36 | No data | — |
| Mon 14 Sept | Vierlingsbeek 09:38 | No data | — |
| Fri 11 Sept | Vierlingsbeek 09:35 | No data | — |
| Thu 10 Sept | Vierlingsbeek 09:39 | No data | — |