Train Arriva 32325 Nijmegen – Venray

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: tomorrow 08:23 from Nijmegen · Wed 18 Nov

Next departure 08:23 tomorrow · Nijmegen
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 8 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 10 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
08:23on time on time
08:26— —
08:32— —
08:36 / 08:37— —
08:45— —
08:51— —
08: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.

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 NovVierlingsbeek 09:07Partial coverage0 min—
Fri 13 NovVierlingsbeek 09:04Partial coverage0 min—
Thu 12 NovCuijk 08:49Partial coverageNo data—
Wed 11 NovVierlingsbeek 09:04Partial coverageNo data—
Tue 10 NovVierlingsbeek 09:04Partial coverage0 min—
Mon 9 NovVierlingsbeek 09:04Partial coverage0 min—
Fri 6 NovVierlingsbeek 09:07No data—
Thu 5 NovVierlingsbeek 09:04No data—
Wed 4 NovVierlingsbeek 09:04Partial coverage0 min—
Tue 3 NovVierlingsbeek 09:04No data—
Mon 2 NovVierlingsbeek 09:04No data—
Fri 30 OctVierlingsbeek 09:05No data—
Thu 29 OctVierlingsbeek 09:06Partial coverage0 min—
Wed 28 OctVierlingsbeek 09:08Partial coverage0 min—
Tue 27 OctVierlingsbeek 09:07Partial coverage0 min—
Mon 26 OctVierlingsbeek 09:05No data—
Fri 16 OctVierlingsbeek 09:07No data—
Thu 15 OctVierlingsbeek 09:05No data—
Mon 12 OctVierlingsbeek 09:07No data—
Fri 9 OctVierlingsbeek 09:06Partial coverage0 min—
Thu 8 OctVierlingsbeek 09:05Partial coverage0 min—
Wed 7 OctVierlingsbeek 09:05Partial coverageNo data—
Tue 6 OctVierlingsbeek 09:05No data—
Mon 5 OctVierlingsbeek 09:05No data—
Fri 2 OctVierlingsbeek 09:07No data—
Thu 1 OctVierlingsbeek 09:06No data—
Wed 30 SeptVierlingsbeek 09:05No data—
Tue 29 SeptVierlingsbeek 09:06No data—
Mon 28 SeptVierlingsbeek 09:07No data—
Fri 25 SeptVierlingsbeek 09:05No data—