Train Arriva 32323 Nijmegen – Venray

Nijmegen 07:53 → Venray 08:28 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Vierlingsbeek at 08:34 0 min

  1. Nijmegen07:53
  2. Nijmegen Heyendaal07:56
  3. Mook-Molenhoek08:02
  4. Cuijk08:06
  5. Boxmeer08:15
  6. Vierlingsbeek08:21
  7. Venray08:28

Next service: tomorrow 07:53 from Nijmegen · Tue 3 Nov

Full trip card
Next departure 07:53 tomorrow · Nijmegen
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 6 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 35 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

Worst days

  • Thu 8 Oct Max en route +6 min · last fix heading to Vierlingsbeek +6 min

Distribution · 90 days

7 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=1
  • 50% T n=2
  • 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).

StopSched.
Nijmegen
07:53
Nijmegen Heyendaal
07:56
Mook-Molenhoek
08:02
Cuijk
08:06 / 08:07
Boxmeer
08:15
Vierlingsbeek
08:21
Venray
08: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

DateLast stopFinalMax
Mon 2 NovVierlingsbeek 08:34Partial coverage0 min—
Fri 30 OctVierlingsbeek 08:35No data—
Thu 29 OctVierlingsbeek 08:38Partial coverage0 min—
Wed 28 OctVierlingsbeek 08:35Partial coverageNo data—
Tue 27 OctVierlingsbeek 08:35Partial coverage0 min—
Mon 26 OctVierlingsbeek 08:37No data—
Fri 16 OctVierlingsbeek 08:35No data—
Thu 15 OctVierlingsbeek 08:36No data—
Mon 12 OctVierlingsbeek 08:36No data—
Fri 9 OctVierlingsbeek 08:38Partial coverage+2 min+2 min
Thu 8 OctVierlingsbeek 08:42Partial coverage+6 min+6 min
Wed 7 OctVierlingsbeek 08:37Partial coverage+1 min+1 min
Tue 6 OctVierlingsbeek 08:37Partial coverage+1 min+1 min
Fri 2 OctVierlingsbeek 08:39No data—
Thu 1 OctVierlingsbeek 08:36No data—
Wed 30 SeptVierlingsbeek 08:36No data—
Tue 29 SeptVierlingsbeek 08:35No data—
Mon 28 SeptVierlingsbeek 08:35No data—
Fri 25 SeptVierlingsbeek 08:35No data—
Thu 24 SeptVierlingsbeek 08:35No data—
Wed 23 SeptVierlingsbeek 08:35No data—
Tue 22 SeptVierlingsbeek 08:36No data—
Mon 21 SeptVierlingsbeek 08:37No data—
Fri 18 SeptVierlingsbeek 08:36No data—
Thu 17 SeptVierlingsbeek 08:35No data—
Wed 16 SeptVierlingsbeek 08:37No data—
Tue 15 SeptVierlingsbeek 08:36No data—
Mon 14 SeptVierlingsbeek 08:38No data—
Fri 11 SeptVierlingsbeek 08:36No data—
Thu 10 SeptVierlingsbeek 08:35No data—