Train Arriva 32335 Nijmegen – Venray

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

It has not run yet today

Last recorded run: Thursday 15 October No data

Next service: today 10:53 from Nijmegen · Fri 16 Oct

Full trip card
Next departure 10:53 today · Nijmegen
On-time · 30 days
—
Too little data (1/19 runs with data)
RT coverage: 0 full · 1 partial · 18 no data
On-time · 90 days
—
Too little data (1/37 runs with data)
RT coverage: 0 full · 1 partial · 36 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

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

  • Early 0% · 0
  • On time 100% · 1
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • 100% T n=1
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 stops).

StopSched.
Nijmegen
10:53
Nijmegen Heyendaal
10:56
Mook-Molenhoek
11:02
Cuijk
11:06 / 11:07
Boxmeer
11:15
Vierlingsbeek
11:21
Venray
11: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
Thu 15 OctVierlingsbeek 11:35No data—
Mon 12 OctVierlingsbeek 11:35No data—
Fri 9 OctVierlingsbeek 11:35No data—
Thu 8 OctVierlingsbeek 11:35Partial coverage0 min—
Wed 7 OctCuijk 12:05No data—
Tue 6 OctVierlingsbeek 11:35No data—
Mon 5 OctVierlingsbeek 11:36No data—
Fri 2 OctVierlingsbeek 11:35No data—
Thu 1 OctVierlingsbeek 11:35No data—
Wed 30 SeptVierlingsbeek 11:36No data—
Tue 29 SeptVierlingsbeek 11:35No data—
Mon 28 SeptVierlingsbeek 11:36No data—
Fri 25 SeptVierlingsbeek 11:35No data—
Thu 24 SeptVierlingsbeek 11:35No data—
Wed 23 SeptVierlingsbeek 11:35No data—
Tue 22 SeptVierlingsbeek 11:35No data—
Mon 21 SeptVierlingsbeek 11:35No data—
Fri 18 SeptVierlingsbeek 11:37No data—
Thu 17 SeptVierlingsbeek 11:36No data—
Wed 16 SeptVierlingsbeek 11:37No data—
Tue 15 SeptVierlingsbeek 11:35No data—
Mon 14 SeptVierlingsbeek 11:36No data—
Fri 11 SeptVierlingsbeek 11:36No data—
Thu 10 SeptVierlingsbeek 11:35No data—
Tue 8 SeptVierlingsbeek 11:36No data—
Mon 7 SeptVierlingsbeek 11:35No data—
Fri 4 SeptVierlingsbeek 11:35No data—
Thu 3 SeptVierlingsbeek 11:35No data—
Wed 2 SeptVierlingsbeek 11:37No data—
Tue 1 SeptVierlingsbeek 11:36No data—