Train Arriva 32331 Nijmegen – Venray

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

✓ Today’s run finished

Today, last fix heading to Vierlingsbeek at 10:36 No data

  1. Nijmegen09:53
  2. Nijmegen Heyendaal09:56
  3. Mook-Molenhoek10:02
  4. Cuijk10:06
  5. Boxmeer10:15
  6. Vierlingsbeek10:21
  7. Venray10:28

Next service: tomorrow 09:53 from Nijmegen · Fri 16 Oct

Next departure 09:53 tomorrow · Nijmegen
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 1 full · 2 partial · 17 no data
On-time · 90 days
67%
2/3 runs under 3 min
RT coverage: 1 full · 2 partial · 34 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 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

Worst days

  • Wed 7 Oct Max en route +6 min · last fix heading to Vierlingsbeek +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 2
  • 3–10 min 33% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 0% W n=1
  • — T n=0
  • 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.
09:53
09:56
10:02
10:06 / 10:07
10:15
10:21
10: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 10:36No data—
Mon 12 OctVierlingsbeek 10:36No data—
Fri 9 OctVierlingsbeek 10:36Partial coverage0 min—
Thu 8 OctVierlingsbeek 10:35No data—
Wed 7 OctVierlingsbeek 12:01+6 min+6 min
Tue 6 OctVierlingsbeek 10:35Partial coverage0 min—
Mon 5 OctVierlingsbeek 10:35No data—
Fri 2 OctVierlingsbeek 10:35No data—
Thu 1 OctVierlingsbeek 10:35No data—
Wed 30 SeptVierlingsbeek 10:36No data—
Tue 29 SeptVierlingsbeek 10:35No data—
Mon 28 SeptVierlingsbeek 10:35No data—
Fri 25 SeptVierlingsbeek 10:36No data—
Thu 24 SeptVierlingsbeek 10:35No data—
Wed 23 SeptVierlingsbeek 10:37No data—
Tue 22 SeptVierlingsbeek 10:36No data—
Mon 21 SeptVierlingsbeek 10:35No data—
Fri 18 SeptVierlingsbeek 10:35No data—
Thu 17 SeptVierlingsbeek 10:35No data—
Wed 16 SeptVierlingsbeek 10:35No data—
Tue 15 SeptVierlingsbeek 10:35No data—
Mon 14 SeptVierlingsbeek 10:36No data—
Fri 11 SeptVierlingsbeek 10:38No data—
Thu 10 SeptVierlingsbeek 10:35No data—
Tue 8 SeptVierlingsbeek 10:40No data—
Mon 7 SeptVierlingsbeek 10:35No data—
Fri 4 SeptVierlingsbeek 10:35No data—
Thu 3 SeptVierlingsbeek 10:35No data—
Wed 2 SeptVierlingsbeek 10:36No data—
Tue 1 SeptVierlingsbeek 10:35No data—