Train Arriva 32276 Venlo → Nijmegen

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

Arriva 32276 Venlo–Nijmegen: final delay under 3 min on 7 of its 7 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 22:07 (GMT+1).

Running now · updated 22:07

Position estimated from the timetable

Heading to Nijmegen No data

Estimated arrival at Nijmegen 22:22 · 77 km/h

  1. Venlo21:29
  2. Blerick21:31
  3. Vierlingsbeek21:50
  4. Boxmeer21:56
  5. Cuijk22:07
  6. Nijmegen Heyendaal22:18
  7. Nijmegen22:22
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 3 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 16 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: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=4
  • 100% S n=6

Stops and timetable

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

Last 90 days, 10 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
21:29on time on time
21:31≈ on time ≈ on time
21:44 / 21:45≈ on time ≈ +1 min
21:50 / 21:51≈ on time ≈ +1 min
21:56 / 22:00≈ on time ≈ +1 min
22:07 / 22:08≈ on time ≈ +1 min
22:12≈ on time ≈ +1 min
22:18≈ on time ≈ +1 min
22: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
Sun 22 NovCuijk 22:04Partial coverage0 min—
Sat 21 NovNijmegen Heyendaal 22:32Partial coverage0 min—
Sun 15 NovNijmegen Heyendaal 22:33+1 min—
Sat 14 NovNijmegen Heyendaal 22:320 min—
Sun 8 NovNijmegen Heyendaal 22:33+1 min+1 min
Sat 7 NovNijmegen Heyendaal 22:320 min—
Sun 1 NovTegelen 21:340 min—
Sat 31 OctTegelen 21:39No data—
Sun 25 OctTegelen 21:35No data—
Sat 24 OctTegelen 21:36No data—
Sun 18 OctTegelen 21:38+2 min+3 min
Sat 17 OctTegelen 21:38No data—
Sun 11 OctNijmegen Heyendaal 22:320 min—
Sat 10 OctBoxmeer 22:140 min—
Sun 4 OctNijmegen Heyendaal 22:33No data—
Sat 3 OctNijmegen Heyendaal 22:32No data—
Sun 27 SeptNijmegen Heyendaal 22:33No data—
Sat 26 SeptNijmegen Heyendaal 22:32No data—
Sun 20 SeptNijmegen Heyendaal 22:32No data—
Sat 19 SeptNijmegen Heyendaal 22:32No data—
Sun 13 SeptNijmegen Heyendaal 22:32No data—
Sat 12 SeptNijmegen Heyendaal 22:32No data—
Sun 6 SeptNijmegen Heyendaal 22:32No data—
Sat 5 SeptNijmegen Heyendaal 22:32No data—
Sun 30 AugNijmegen Heyendaal 22:33No data—
Sat 29 AugNijmegen Heyendaal 22:32No data—