Train Arriva 32355 Nijmegen – Venray

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

It has not run yet today

Last recorded run: Friday 16 October No data

Next service: today 15:53 from Nijmegen · Mon 26 Oct

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

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

StopSched.
15:53
15:56
16:02
16:06 / 16:07
16:15
16:21
16: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
Fri 16 OctVierlingsbeek 16:35No data—
Thu 15 OctVierlingsbeek 16:37No data—
Mon 12 OctVierlingsbeek 16:37Partial coverage+1 min+1 min
Fri 9 OctVierlingsbeek 16:36Partial coverage+1 min—
Thu 8 OctVierlingsbeek 16:35Partial coverage0 min—
Wed 7 OctVierlingsbeek 16:35No data—
Tue 6 OctVierlingsbeek 16:36Partial coverage0 min—
Mon 5 OctVierlingsbeek 16:37Partial coverage+1 min—
Fri 2 OctVierlingsbeek 16:38No data—
Thu 1 OctVierlingsbeek 16:35No data—
Wed 30 SeptVierlingsbeek 16:35No data—
Tue 29 SeptVierlingsbeek 16:36No data—
Mon 28 SeptVierlingsbeek 16:35No data—
Fri 25 SeptVierlingsbeek 16:37No data—
Thu 24 SeptVierlingsbeek 16:36No data—
Wed 23 SeptVierlingsbeek 16:36No data—
Tue 22 SeptVierlingsbeek 16:36No data—
Mon 21 SeptVierlingsbeek 16:37No data—
Fri 18 SeptVierlingsbeek 16:37No data—
Thu 17 SeptVierlingsbeek 16:37No data—
Wed 16 SeptVierlingsbeek 16:37No data—
Tue 15 SeptVierlingsbeek 16:35No data—
Mon 14 SeptVierlingsbeek 16:36No data—
Fri 11 SeptVierlingsbeek 16:36No data—
Tue 8 SeptVierlingsbeek 16:38No data—
Mon 7 SeptVierlingsbeek 16:36No data—
Fri 4 SeptVierlingsbeek 16:39No data—
Thu 3 SeptVierlingsbeek 16:36No data—
Wed 2 SeptVierlingsbeek 16:36No data—
Tue 1 SeptVierlingsbeek 16:38No data—