Train Arriva 32260 Venlo – Nijmegen

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

Running now · updated 17:51

Position estimated from the timetable

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 18:22 · 79 km/h

  1. Venlo17:29
  2. Blerick17:31
  3. Vierlingsbeek17:50
  4. Boxmeer17:56
  5. Cuijk18:07
  6. Nijmegen Heyendaal18:18
  7. Nijmegen18:22

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 partial · 9 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 28 full · 3 partial · 57 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

  • Thu 19 Nov Max en route +5 min · last fix heading to Nijmegen Heyendaal +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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