Train Arriva 32347 Nijmegen – Venray

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

✓ Today’s run finished

Today, last fix heading to Vierlingsbeek at 14:35 No data

  1. Nijmegen13:53
  2. Nijmegen Heyendaal13:56
  3. Mook-Molenhoek14:02
  4. Cuijk14:06
  5. Boxmeer14:15
  6. Vierlingsbeek14:21
  7. Venray14:28

Next service: tomorrow 13:53 from Nijmegen · Tue 13 Oct

Next departure 13:53 tomorrow · Nijmegen
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 16 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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=1
  • 100% T n=1
  • 100% W n=1
  • 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.
13:53
13:56
14:02
14:06 / 14:07
14:15
14:21
14: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
Mon 12 OctVierlingsbeek 14:35No data—
Fri 9 OctVierlingsbeek 14:36Partial coverage+1 min—
Thu 8 OctVierlingsbeek 14:36Partial coverage0 min—
Wed 7 OctVierlingsbeek 14:35Partial coverage0 min—
Tue 6 OctVierlingsbeek 14:36Partial coverage0 min—
Mon 5 OctVierlingsbeek 14:35Partial coverage0 min—
Fri 2 OctVierlingsbeek 14:36No data—
Thu 1 OctVierlingsbeek 14:35No data—
Wed 30 SeptVierlingsbeek 14:35No data—
Tue 29 SeptVierlingsbeek 14:36No data—
Mon 28 SeptVierlingsbeek 14:38No data—
Fri 25 SeptVierlingsbeek 14:35No data—
Thu 24 SeptVierlingsbeek 14:37No data—
Wed 23 SeptVierlingsbeek 14:35No data—
Tue 22 SeptVierlingsbeek 14:38No data—
Mon 21 SeptVierlingsbeek 14:37No data—
Fri 18 SeptVierlingsbeek 14:35No data—
Thu 17 SeptVierlingsbeek 14:36No data—
Wed 16 SeptVierlingsbeek 14:37No data—
Tue 15 SeptVierlingsbeek 14:36No data—
Mon 14 SeptVierlingsbeek 14:36No data—
Fri 11 SeptVierlingsbeek 14:36No data—
Thu 10 SeptVierlingsbeek 14:35No data—
Tue 8 SeptVierlingsbeek 14:35No data—
Mon 7 SeptVierlingsbeek 14:38No data—
Fri 4 SeptVierlingsbeek 14:39No data—
Thu 3 SeptVierlingsbeek 14:37No data—
Wed 2 SeptVierlingsbeek 14:38No data—
Tue 1 SeptVierlingsbeek 14:38No data—
Mon 31 AugVierlingsbeek 14:37No data—