Train Arriva 32256 Venlo – Nijmegen

Venlo 16:29 → Nijmegen 17:22 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 16:29 from Venlo · Thu 19 Nov

Next departure 16:29 today · Venlo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 28 full · 1 partial · 58 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Fri 13 Nov Max en route +5 min · last fix heading to Nijmegen Heyendaal +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=2
  • 67% F n=3
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 29 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
16:29on time on time
16:31≈ on time ≈ on time
16:44 / 16:45≈ on time ≈ +1 min
16:50 / 16:51≈ on time ≈ +1 min
16:56 / 17:00≈ on time ≈ +1 min
17:07 / 17:08≈ on time ≈ +1 min
17:12≈ on time ≈ +1 min
17:18≈ +1 min ≈ +2 min
17:22+1 min +2 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
Wed 18 NovNijmegen Heyendaal 17:32Partial coverage+1 min—
Tue 17 NovNijmegen Heyendaal 17:32+3 min+3 min
Mon 16 NovNijmegen Heyendaal 17:33+2 min+2 min
Sun 15 NovNijmegen Heyendaal 17:34+1 min+2 min
Sat 14 NovNijmegen Heyendaal 17:320 min—
Fri 13 NovNijmegen Heyendaal 17:37+5 min+5 min
Thu 12 NovNijmegen Heyendaal 17:32+1 min—
Wed 11 NovNijmegen Heyendaal 17:33+1 min—
Tue 10 NovNijmegen Heyendaal 17:32+1 min—
Mon 9 NovNijmegen Heyendaal 17:32+2 min+2 min
Sun 8 NovNijmegen Heyendaal 17:320 min—
Sat 7 NovNijmegen Heyendaal 17:320 min—
Fri 6 NovNijmegen Heyendaal 17:330 min—
Thu 5 NovNijmegen Heyendaal 17:32No data—
Wed 4 NovNijmegen Heyendaal 17:320 min—
Tue 3 NovNijmegen Heyendaal 17:32No data—
Mon 2 NovNijmegen Heyendaal 17:32No data—
Sun 1 NovTegelen 16:38+2 min+3 min
Sat 31 OctTegelen 16:37+1 min+1 min
Fri 30 OctNijmegen Heyendaal 17:32No data—
Thu 29 OctNijmegen Heyendaal 17:32No data—
Wed 28 OctNijmegen Heyendaal 17:320 min—
Tue 27 OctNijmegen Heyendaal 17:320 min—
Mon 26 OctNijmegen Heyendaal 17:32No data—
Sun 25 OctTegelen 16:38No data—
Sat 24 OctTegelen 16:36+1 min+1 min
Fri 23 OctTegelen 16:36No data—
Thu 22 OctTegelen 16:37No data—
Wed 21 OctTegelen 16:36No data—
Tue 20 OctTegelen 16:360 min—