Train Arriva 32360 Venray – Nijmegen

Venray 18:03 → Nijmegen 18:37 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 7 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:03 from Venray · Thu 5 Nov

Next departure 18:03 today · Venray
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 0 full · 4 partial · 7 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Nijmegen, 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

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

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

On-time by weekday

  • 100% M n=3
  • — T n=0
  • 100% W n=2
  • — 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).

Last 90 days, 5 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
18:03on time on time
18:08 / 18:09— —
18:14 / 18:15— —
18:22 / 18:23— —
18:27— —
18:33— —
18:37— —

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
Wed 4 NovBoxmeer 18:29Partial coverage0 min—
Mon 2 NovVierlingsbeek 18:23No data—
Fri 30 OctNijmegen Heyendaal 18:47No data—
Wed 28 OctVierlingsbeek 18:23Partial coverage0 min—
Mon 26 OctVierlingsbeek 18:23Partial coverage0 min—
Fri 16 OctNijmegen Heyendaal 18:50No data—
Thu 15 OctMook-Molenhoek 18:41No data—
Mon 12 OctNijmegen Heyendaal 18:47Partial coverage0 min—
Fri 9 OctNijmegen Heyendaal 18:47No data—
Thu 8 OctVenray 18:17No data—
Wed 7 OctVierlingsbeek 18:23No data—
Tue 6 OctVenray 18:17No data—
Mon 5 OctVierlingsbeek 18:23Partial coverage0 min—
Fri 2 OctNijmegen Heyendaal 18:47No data—
Thu 1 OctVenray 18:18No data—
Wed 30 SeptVierlingsbeek 18:18No data—
Tue 29 SeptVenray 18:17No data—
Mon 28 SeptVenray 18:17No data—
Fri 25 SeptNijmegen Heyendaal 18:47No data—
Wed 23 SeptVierlingsbeek 18:23No data—
Tue 22 SeptVenray 18:17No data—
Mon 21 SeptVenray 18:17No data—
Fri 18 SeptNijmegen Heyendaal 18:47No data—
Thu 17 SeptVierlingsbeek 18:23No data—
Wed 16 SeptVenray 18:17No data—
Tue 15 SeptVierlingsbeek 18:23No data—
Mon 14 SeptVierlingsbeek 18:23No data—
Fri 11 SeptNijmegen Heyendaal 18:43No data—
Tue 8 SeptVenray 18:18No data—
Mon 7 SeptCuijk 18:37No data—