Train Arriva 32333 Nijmegen – Venray

Nijmegen 10:23 → Venray 10:58 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Vierlingsbeek at 11:05 No data

  1. Nijmegen10:23
  2. Nijmegen Heyendaal10:26
  3. Mook-Molenhoek10:32
  4. Cuijk10:36
  5. Boxmeer10:45
  6. Vierlingsbeek10:51
  7. Venray10:58

Next service: tomorrow 10:23 from Nijmegen · Tue 13 Oct

Next departure 10:23 tomorrow · Nijmegen
On-time · 30 days
—
Too little data (2/21 runs with data)
RT coverage: 1 full · 1 partial · 19 no data
On-time · 90 days
—
Too little data (2/36 runs with data)
RT coverage: 1 full · 1 partial · 34 no data
Typical delay
—
Needs at least 5 runs with data (2 so far)
P90
—
Needs at least 5 runs with data (2 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

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

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

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 100% W n=1
  • — T n=0
  • — 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.
10:23
10:26
10:32
10:36 / 10:37
10:45
10:51
10:58

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 12 OctVierlingsbeek 11:05No data—
Fri 9 OctVierlingsbeek 11:05No data—
Thu 8 OctVierlingsbeek 11:05No data—
Wed 7 OctMook-Molenhoek 12:020 min—
Tue 6 OctVierlingsbeek 11:06Partial coverage0 min—
Mon 5 OctVierlingsbeek 11:07No data—
Fri 2 OctVierlingsbeek 11:06No data—
Thu 1 OctVierlingsbeek 11:05No data—
Wed 30 SeptVierlingsbeek 11:07No data—
Tue 29 SeptVierlingsbeek 11:05No data—
Mon 28 SeptVierlingsbeek 11:05No data—
Fri 25 SeptVierlingsbeek 11:05No data—
Thu 24 SeptVierlingsbeek 11:05No data—
Wed 23 SeptVierlingsbeek 11:05No data—
Tue 22 SeptVierlingsbeek 11:05No data—
Mon 21 SeptVierlingsbeek 11:05No data—
Fri 18 SeptVierlingsbeek 11:05No data—
Thu 17 SeptVierlingsbeek 11:05No data—
Wed 16 SeptVierlingsbeek 11:06No data—
Tue 15 SeptVierlingsbeek 11:07No data—
Mon 14 SeptVierlingsbeek 11:06No data—
Fri 11 SeptVierlingsbeek 11:09No data—
Thu 10 SeptVierlingsbeek 11:07No data—
Tue 8 SeptVierlingsbeek 11:09No data—
Mon 7 SeptVierlingsbeek 11:15No data—
Fri 4 SeptVierlingsbeek 11:05No data—
Thu 3 SeptVierlingsbeek 11:06No data—
Wed 2 SeptVierlingsbeek 11:06No data—
Tue 1 SeptVierlingsbeek 11:05No data—
Mon 31 AugVierlingsbeek 11:08No data—