Train Arriva 32357 Nijmegen – Venray

Nijmegen 16:23 → Venray 16: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 +2 min

Next service: today 16:23 from Nijmegen · Tue 17 Nov

Next departure 16:23 today · Nijmegen
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 8 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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=3
  • 100% T n=3
  • 100% W n=2
  • 100% T n=1
  • 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, 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
16:23on time on time
16:26— —
16:32— —
16:36 / 16:37— —
16:45— —
16:51— —
16: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 17:09Partial coverage+2 min+2 min
Thu 12 NovVierlingsbeek 17:04Partial coverage0 min—
Wed 11 NovVierlingsbeek 17:04Partial coverage+2 min+3 min
Tue 10 NovVierlingsbeek 17:04Partial coverage+1 min—
Mon 9 NovVierlingsbeek 17:04No data—
Fri 6 NovVierlingsbeek 17:09No data—
Thu 5 NovVierlingsbeek 17:04No data—
Wed 4 NovVierlingsbeek 17:04No data—
Tue 3 NovVierlingsbeek 17:05No data—
Fri 30 OctVierlingsbeek 17:06No data—
Thu 29 OctVierlingsbeek 17:05No data—
Wed 28 OctVierlingsbeek 17:05Partial coverage0 min—
Tue 27 OctVierlingsbeek 17:07Partial coverage0 min—
Mon 26 OctVierlingsbeek 17:05No data—
Fri 16 OctVierlingsbeek 17:05No data—
Thu 15 OctVierlingsbeek 17:06No data—
Mon 12 OctVierlingsbeek 17:06Partial coverage0 min—
Fri 9 OctVierlingsbeek 17:06Partial coverage0 min—
Thu 8 OctVierlingsbeek 17:05No data—
Wed 7 OctVierlingsbeek 17:05Partial coverageNo data—
Tue 6 OctVierlingsbeek 17:05Partial coverage0 min—
Mon 5 OctVierlingsbeek 17:05Partial coverage0 min—
Fri 2 OctVierlingsbeek 17:07No data—
Thu 1 OctVierlingsbeek 17:05No data—
Wed 30 SeptVierlingsbeek 17:01No data—
Tue 29 SeptVierlingsbeek 17:05No data—
Mon 28 SeptVierlingsbeek 17:05No data—
Fri 25 SeptVierlingsbeek 17:05No data—
Thu 24 SeptVierlingsbeek 17:05No data—
Wed 23 SeptVierlingsbeek 17:04No data—