Train Arriva 32334 Venray – Nijmegen

Venray 11:33 → Nijmegen 12:07 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 7 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 11:33 from Venray · Tue 17 Nov

Next departure 11:33 today · Venray
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 9 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

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

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

  • Early 0% · 0
  • On time 100% · 9
  • 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=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).

Last 90 days, 9 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.

StopSched.Usually 9 days in 10
11:33on time on time
11:38 / 11:39— —
11:44 / 11:45— —
11:52 / 11:53— —
11:57— —
12:03— —
12:07— —

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

DateLast stopFinalMax
Mon 16 NovNijmegen Heyendaal 12:18Partial coverage+1 min—
Fri 13 NovNijmegen Heyendaal 12:18Partial coverage0 min—
Thu 12 NovNijmegen Heyendaal 12:17Partial coverage0 min—
Wed 11 NovNijmegen Heyendaal 12:17No data—
Tue 10 NovNijmegen Heyendaal 12:18Partial coverage+1 min—
Mon 9 NovNijmegen Heyendaal 12:17No data—
Fri 6 NovNijmegen Heyendaal 12:17No data—
Thu 5 NovNijmegen Heyendaal 12:17No data—
Wed 4 NovNijmegen Heyendaal 12:19Partial coverage+1 min+1 min
Tue 3 NovNijmegen Heyendaal 12:17No data—
Mon 2 NovNijmegen Heyendaal 12:17No data—
Fri 30 OctNijmegen Heyendaal 12:17No data—
Thu 29 OctNijmegen Heyendaal 12:17No data—
Wed 28 OctNijmegen Heyendaal 12:17Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 12:17Partial coverage0 min—
Mon 26 OctNijmegen Heyendaal 12:17No data—
Fri 16 OctNijmegen Heyendaal 12:18No data—
Thu 15 OctNijmegen Heyendaal 12:17No data—
Mon 12 OctNijmegen Heyendaal 12:17No data—
Fri 9 OctNijmegen Heyendaal 12:17No data—
Thu 8 OctNijmegen Heyendaal 12:18Partial coverage+1 min—
Wed 7 OctNijmegen Heyendaal 12:17Partial coverage0 min—
Tue 6 OctNijmegen Heyendaal 12:17No data—
Mon 5 OctNijmegen Heyendaal 12:18No data—
Fri 2 OctNijmegen Heyendaal 12:17No data—
Thu 1 OctNijmegen Heyendaal 12:17No data—
Wed 30 SeptNijmegen Heyendaal 12:19No data—
Tue 29 SeptNijmegen Heyendaal 12:20No data—
Mon 28 SeptNijmegen Heyendaal 12:17No data—
Fri 25 SeptNijmegen Heyendaal 12:17No data—