Train Arriva 32347 Nijmegen – Venray
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 13:53 from Nijmegen · Mon 9 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
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 8
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=2
- 100% W n=3
- 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).
Last 90 days, 8 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 |
|---|---|---|---|
| 13:53 | on time | on time | |
| 13:56 | — | — | |
| 14:02 | — | — | |
| 14:06 / 14:07 | — | — | |
| 14:15 | — | — | |
| 14:21 | — | — | |
| 14: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.
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 6 Nov | Vierlingsbeek 14:34 | No data | — |
| Thu 5 Nov | Vierlingsbeek 14:34 | No data | — |
| Wed 4 Nov | Vierlingsbeek 14:34Partial coverage | 0 min | — |
| Tue 3 Nov | Vierlingsbeek 14:34 | No data | — |
| Mon 2 Nov | Vierlingsbeek 14:39 | No data | — |
| Fri 30 Oct | Vierlingsbeek 14:35 | No data | — |
| Thu 29 Oct | Vierlingsbeek 14:35 | No data | — |
| Wed 28 Oct | Vierlingsbeek 14:48Partial coverage | 0 min | — |
| Tue 27 Oct | Vierlingsbeek 14:35Partial coverage | 0 min | — |
| Mon 26 Oct | Vierlingsbeek 14:35 | No data | — |
| Fri 16 Oct | Vierlingsbeek 14:39 | No data | — |
| Thu 15 Oct | Vierlingsbeek 14:36 | No data | — |
| Mon 12 Oct | Vierlingsbeek 14:35 | No data | — |
| Fri 9 Oct | Vierlingsbeek 14:36Partial coverage | +1 min | — |
| Thu 8 Oct | Vierlingsbeek 14:36Partial coverage | 0 min | — |
| Wed 7 Oct | Vierlingsbeek 14:35Partial coverage | 0 min | — |
| Tue 6 Oct | Vierlingsbeek 14:36Partial coverage | 0 min | — |
| Mon 5 Oct | Vierlingsbeek 14:35Partial coverage | 0 min | — |
| Fri 2 Oct | Vierlingsbeek 14:36 | No data | — |
| Thu 1 Oct | Vierlingsbeek 14:35 | No data | — |
| Wed 30 Sept | Vierlingsbeek 14:35 | No data | — |
| Tue 29 Sept | Vierlingsbeek 14:36 | No data | — |
| Mon 28 Sept | Vierlingsbeek 14:38 | No data | — |
| Fri 25 Sept | Vierlingsbeek 14:35 | No data | — |
| Thu 24 Sept | Vierlingsbeek 14:37 | No data | — |
| Wed 23 Sept | Vierlingsbeek 14:35 | No data | — |
| Tue 22 Sept | Vierlingsbeek 14:38 | No data | — |
| Mon 21 Sept | Vierlingsbeek 14:37 | No data | — |
| Fri 18 Sept | Vierlingsbeek 14:35 | No data | — |
| Thu 17 Sept | Vierlingsbeek 14:36 | No data | — |