Train Arriva 32246 Venlo – Nijmegen

Venlo 13:59 → Nijmegen 14:52 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 13:59 from Venlo · Fri 20 Nov

Next departure 13:59 today · Venlo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 17 full · 2 partial · 10 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 24 full · 2 partial · 61 no data
Typical delay
0min
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

  • Thu 12 Nov Max en route +14 min · last fix heading to Nijmegen Heyendaal +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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