Train Arriva 32316 Venlo – Nijmegen

Venlo 06:42 → Nijmegen 07:37 Mon, Tue, Wed, Thu, Fri 0 h 55 min · 9 stops Arriva

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 06:42 from Venlo · Mon 9 Nov

Next departure 06:42 tomorrow · Venlo
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 5 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 34 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 Nijmegen, 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 28 Oct Max en route +3 min · last fix heading to Nijmegen Heyendaal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 50% W n=2
  • 100% T n=3
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 12 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
06:42on time on time
06:45— —
07:02 / 07:03— —
07:08 / 07:09— —
07:14 / 07:15— —
07:22 / 07:23— —
07:27— —
07:33— —
07: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
Fri 6 NovNijmegen Heyendaal 07:48No data—
Thu 5 NovNijmegen Heyendaal 07:49No data—
Wed 4 NovNijmegen Heyendaal 07:47No data—
Tue 3 NovNijmegen Heyendaal 07:49Partial coverage0 min—
Mon 2 NovNijmegen Heyendaal 07:47Partial coverage0 min—
Fri 30 OctNijmegen Heyendaal 07:47Partial coverage0 min—
Thu 29 OctNijmegen Heyendaal 07:47Partial coverage0 min—
Wed 28 OctNijmegen Heyendaal 07:53Partial coverage+3 min+3 min
Tue 27 OctNijmegen Heyendaal 07:47Partial coverage0 min—
Mon 26 OctNijmegen Heyendaal 07:47Partial coverage0 min—
Fri 16 OctNijmegen Heyendaal 07:47No data—
Thu 15 OctNijmegen Heyendaal 07:47Partial coverage0 min—
Mon 12 OctNijmegen Heyendaal 07:47No data—
Fri 9 OctNijmegen Heyendaal 07:48Partial coverage+1 min—
Thu 8 OctNijmegen Heyendaal 07:48Partial coverage+1 min+1 min
Wed 7 OctNijmegen Heyendaal 07:48Partial coverage0 min—
Tue 6 OctNijmegen Heyendaal 07:49Partial coverage+1 min+1 min
Fri 2 OctNijmegen Heyendaal 07:47No data—
Thu 1 OctNijmegen Heyendaal 07:47No data—
Wed 30 SeptNijmegen Heyendaal 07:47No data—
Tue 29 SeptNijmegen Heyendaal 07:47No data—
Mon 28 SeptNijmegen Heyendaal 07:47No data—
Fri 25 SeptNijmegen Heyendaal 07:47No data—
Thu 24 SeptNijmegen Heyendaal 07:56No data—
Wed 23 SeptNijmegen Heyendaal 07:49No data—
Tue 22 SeptNijmegen Heyendaal 07:47No data—
Mon 21 SeptNijmegen Heyendaal 07:47No data—
Fri 18 SeptNijmegen Heyendaal 07:47No data—
Thu 17 SeptNijmegen Heyendaal 07:57No data—
Wed 16 SeptNijmegen Heyendaal 07:48No data—