Train Arriva 32361 Nijmegen – Venray

Nijmegen 17:23 → Venray 17: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 +1 min

Next service: today 17:23 from Nijmegen · Wed 18 Nov

Next departure 17:23 today · Nijmegen
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 0 full · 10 partial · 4 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 36 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Wed 11 Nov Max en route +4 min · last fix heading to Vierlingsbeek +4 min
  • Mon 26 Oct Max en route +3 min · last fix heading to Vierlingsbeek +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 67% W n=3
  • 100% T n=1
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
17:23on time on time
17:26— —
17:32— —
17:36 / 17:37— —
17:45— —
17:51— —
17: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 18:05Partial coverage+1 min—
Fri 13 NovVierlingsbeek 18:04Partial coverage+1 min+2 min
Thu 12 NovVierlingsbeek 18:04Partial coverage+2 min+2 min
Wed 11 NovVierlingsbeek 18:04Partial coverage+4 min+4 min
Tue 10 NovVierlingsbeek 18:04Partial coverage+2 min+2 min
Mon 9 NovVierlingsbeek 18:04Partial coverage+2 min+2 min
Fri 6 NovVierlingsbeek 18:04Partial coverage+1 min+1 min
Thu 5 NovVierlingsbeek 18:04No data—
Wed 4 NovVierlingsbeek 18:04Partial coverage0 min—
Mon 2 NovVierlingsbeek 18:04No data—
Fri 30 OctVierlingsbeek 18:05No data—
Thu 29 OctVierlingsbeek 18:05No data—
Wed 28 OctVierlingsbeek 18:05Partial coverage0 min—
Mon 26 OctVierlingsbeek 18:05Partial coverage+3 min+3 min
Fri 16 OctVierlingsbeek 18:06No data—
Thu 15 OctVierlingsbeek 18:05No data—
Mon 12 OctVierlingsbeek 18:05Partial coverage0 min—
Fri 9 OctVierlingsbeek 18:05Partial coverage0 min—
Thu 8 OctVierlingsbeek 18:06No data—
Wed 7 OctVierlingsbeek 18:05No data—
Tue 6 OctVierlingsbeek 18:05Partial coverage0 min—
Mon 5 OctVierlingsbeek 18:05Partial coverage0 min—
Fri 2 OctVierlingsbeek 18:05No data—
Thu 1 OctVierlingsbeek 18:05No data—
Wed 30 SeptVierlingsbeek 18:05No data—
Tue 29 SeptVierlingsbeek 18:05No data—
Mon 28 SeptVierlingsbeek 18:05No data—
Fri 25 SeptVierlingsbeek 18:05No data—
Thu 24 SeptVierlingsbeek 18:06No data—
Wed 23 SeptVierlingsbeek 18:05No data—