Train Arriva 32254 Venlo – Nijmegen

Venlo 15:59 → Nijmegen 16:52 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 15:59 from Venlo · Thu 19 Nov

Next departure 15:59 today · Venlo
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 17 full · 1 partial · 11 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 27 full · 1 partial · 59 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 14 Nov Max en route +4 min · last fix heading to Nijmegen Heyendaal +4 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Nijmegen Heyendaal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=2
  • 75% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 28 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
15:59on time on time
16:01≈ on time ≈ on time
16:14 / 16:15≈ on time ≈ on time
16:20 / 16:21≈ on time ≈ +1 min
16:26 / 16:30≈ on time ≈ +1 min
16:37 / 16:38≈ on time ≈ +1 min
16:42≈ on time ≈ +1 min
16:48≈ on time ≈ +1 min
16:52on time +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:02Partial coverage0 min—
Tue 17 NovNijmegen Heyendaal 17:04+2 min+2 min
Mon 16 NovNijmegen Heyendaal 17:05+4 min+4 min
Sun 15 NovNijmegen Heyendaal 17:020 min—
Sat 14 NovNijmegen Heyendaal 17:04+4 min+4 min
Fri 13 NovNijmegen Heyendaal 17:03+1 min+1 min
Thu 12 NovNijmegen Heyendaal 17:020 min—
Wed 11 NovNijmegen Heyendaal 17:020 min—
Tue 10 NovNijmegen Heyendaal 17:020 min—
Mon 9 NovNijmegen Heyendaal 17:020 min—
Sun 8 NovNijmegen Heyendaal 17:030 min—
Sat 7 NovNijmegen Heyendaal 17:020 min—
Fri 6 NovNijmegen Heyendaal 17:04No data—
Thu 5 NovNijmegen Heyendaal 17:02No data—
Wed 4 NovNijmegen Heyendaal 17:020 min—
Tue 3 NovNijmegen Heyendaal 17:020 min—
Mon 2 NovNijmegen Heyendaal 17:020 min—
Sun 1 NovTegelen 16:06No data—
Sat 31 OctTegelen 16:05No data—
Fri 30 OctNijmegen Heyendaal 17:02No data—
Thu 29 OctNijmegen Heyendaal 17:020 min—
Wed 28 OctNijmegen Heyendaal 17:270 min—
Tue 27 OctNijmegen Heyendaal 17:03No data—
Mon 26 OctNijmegen Heyendaal 17:03No data—
Sun 25 OctTegelen 16:06No data—
Sat 24 OctTegelen 16:06+1 min+1 min
Fri 23 OctTegelen 16:07No data—
Thu 22 OctTegelen 16:07No data—
Wed 21 OctTegelen 16:07No data—
Tue 20 OctTegelen 16:060 min—