Train Arriva 32216 Venlo – Nijmegen

Venlo 06:29 → Nijmegen 07:22 Mon, Tue, Wed, Thu, Fri, Sat 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 07:34 +2 min

  1. Venlo06:29
  2. Blerick06:31
  3. Vierlingsbeek06:50
  4. Boxmeer06:56
  5. Cuijk07:07
  6. Nijmegen Heyendaal07:18
  7. Nijmegen07:22

Next service: Monday 06:29 from Venlo · Mon 9 Nov

Next departure 06:29 Monday · Venlo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 17 full · 2 partial · 3 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 20 full · 2 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 10 Oct Max en route +13 min · last fix heading to Nijmegen Heyendaal +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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:29on time on time
06:31≈ on time ≈ on time
06:44 / 06:45≈ on time ≈ on time
06:50 / 06:51≈ on time ≈ +1 min
06:56 / 07:00≈ on time ≈ +1 min
07:07 / 07:08≈ on time ≈ +1 min
07:12≈ on time ≈ +1 min
07:18≈ on time ≈ +1 min
07:22on time +1 min

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
Sat 7 NovNijmegen Heyendaal 07:34Partial coverage+2 min+2 min
Fri 6 NovNijmegen Heyendaal 07:34No data—
Thu 5 NovNijmegen Heyendaal 07:340 min—
Wed 4 NovNijmegen Heyendaal 07:34+1 min+1 min
Tue 3 NovNijmegen Heyendaal 07:320 min—
Mon 2 NovNijmegen Heyendaal 07:34No data—
Fri 30 OctNijmegen Heyendaal 07:320 min—
Thu 29 OctNijmegen Heyendaal 07:320 min—
Wed 28 OctNijmegen Heyendaal 07:35+2 min+2 min
Tue 27 OctNijmegen Heyendaal 07:320 min—
Mon 26 OctNijmegen Heyendaal 07:33+1 min—
Fri 23 OctTegelen 06:37+1 min+1 min
Thu 22 OctTegelen 06:360 min—
Wed 21 OctTegelen 06:35No data—
Tue 20 OctTegelen 06:37+1 min+1 min
Mon 19 OctTegelen 06:350 min—
Fri 16 OctNijmegen Heyendaal 07:320 min—
Thu 15 OctNijmegen Heyendaal 07:340 min—
Tue 13 OctNijmegen Heyendaal 07:330 min—
Mon 12 OctNijmegen Heyendaal 07:330 min—
Sat 10 OctNijmegen Heyendaal 07:43Partial coverage+11 min+13 min
Fri 9 OctNijmegen Heyendaal 07:33+1 min—
Thu 8 OctNijmegen Heyendaal 07:340 min+1 min
Wed 7 OctNijmegen Heyendaal 07:330 min—
Tue 6 OctNijmegen Heyendaal 07:330 min—
Mon 5 OctNijmegen Heyendaal 07:34No data—
Sat 3 OctNijmegen Heyendaal 07:33No data—
Fri 2 OctNijmegen Heyendaal 07:32No data—
Thu 1 OctNijmegen Heyendaal 07:33No data—
Wed 30 SeptNijmegen Heyendaal 07:34No data—