Train Arriva 32266 Venlo – Nijmegen

Venlo 18:59 → Nijmegen 19:52 Daily 0 h 53 min · 9 stops Arriva

Running now · updated 18:46

Position estimated from the timetable

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 19:52

  1. Venlo18:59
  2. Blerick19:01
  3. Vierlingsbeek19:20
  4. Boxmeer19:26
  5. Cuijk19:37
  6. Nijmegen Heyendaal19:48
  7. Nijmegen19:52

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

On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 8 full · 1 partial · 5 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 15 Nov Max en route +15 min · last fix heading to Nijmegen Heyendaal +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=4
  • 100% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 14 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
18:59on time on time
19:01≈ on time ≈ +1 min
19:14 / 19:15≈ on time ≈ +1 min
19:20 / 19:21≈ on time ≈ +1 min
19:26 / 19:30≈ on time ≈ +1 min
19:37 / 19:38≈ on time ≈ +1 min
19:42≈ on time ≈ +1 min
19:48≈ on time ≈ +1 min
19:52on 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 NovVenlo 18:45Partial coverage0 min—
Sun 15 NovNijmegen Heyendaal 20:17+15 min+15 min
Sat 14 NovNijmegen Heyendaal 20:020 min—
Fri 13 NovTegelen 19:040 min—
Sun 8 NovNijmegen Heyendaal 20:020 min—
Sat 7 NovNijmegen Heyendaal 20:020 min—
Fri 6 NovReuver 18:590 min—
Sun 1 NovTegelen 19:08+1 min+2 min
Sat 31 OctTegelen 19:060 min—
Fri 30 OctTegelen 19:05No data—
Sun 25 OctTegelen 19:05No data—
Sat 24 OctTegelen 19:06No data—
Fri 23 OctTegelen 19:06No data—
Thu 22 OctReuver 18:59No data—
Wed 21 OctSwalmen 18:53No data—
Tue 20 OctReuver 18:50No data—
Mon 19 OctSwalmen 18:53No data—
Sun 18 OctTegelen 19:07+1 min+1 min
Sat 17 OctTegelen 19:06No data—
Fri 16 OctNijmegen Heyendaal 20:03No data—
Tue 13 OctSwalmen 18:50No data—
Mon 12 OctReuver 18:590 min—
Sun 11 OctNijmegen Heyendaal 20:020 min—
Sat 10 OctNijmegen Heyendaal 20:030 min—
Fri 9 OctRoermond 18:480 min—
Sun 4 OctNijmegen Heyendaal 20:03No data—
Sat 3 OctNijmegen Heyendaal 20:05No data—
Fri 2 OctReuver 18:59No data—
Sun 27 SeptNijmegen Heyendaal 20:02No data—
Sat 26 SeptNijmegen Heyendaal 20:03No data—