Train Arriva 32271 Nijmegen → Venlo

Nijmegen 19:38 → Venlo 20:31 Daily 0 h 53 min · 9 stops Arriva

Arriva 32271 Nijmegen–Venlo: final delay under 3 min on 5 of its 6 runs with data in the last 30 days (83%). Median final delay: 0 min. Running now, on time. Expected at Venlo: 20:31. TrainsRadar data as of 22 Nov 2026, 20:21 (GMT+1).

Running now · updated 20:21

Position estimated from the timetable

Heading to Venlo 0 min

Estimated arrival at Venlo 20:31 · 98 km/h

  1. Nijmegen19:38
  2. Nijmegen Heyendaal19:41
  3. Cuijk19:50
  4. Boxmeer19:59
  5. Vierlingsbeek20:07
  6. Blerick20:28
  7. Venlo20:31

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

On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 4 full · 2 partial · 4 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 7 full · 2 partial · 18 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: +3 min

Last 30 days

Arrival delay at Venlo, 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 +6 min · last fix heading to Swalmen +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 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
  • 80% S n=5

Stops and timetable

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

Last 90 days, 9 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
19:38on time on time
19:41≈ on time ≈ on time
19:46≈ on time ≈ on time
19:50 / 19:52≈ on time ≈ +1 min
19:59 / 20:02≈ on time ≈ +1 min
20:07 / 20:08≈ on time ≈ +1 min
20:14 / 20:15≈ on time ≈ +2 min
20:28≈ on time ≈ +2 min
20:31on 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
Sun 22 NovBlerick 20:19Partial coverage0 min—
Sat 21 NovBlerick 20:43Partial coverage0 min—
Sun 15 NovSwalmen 21:09+6 min+6 min
Sat 14 NovSwalmen 21:040 min+1 min
Sun 8 NovSwalmen 21:040 min—
Sat 7 NovSwalmen 21:040 min—
Sun 1 NovSwalmen 21:04No data—
Sat 31 OctSwalmen 21:06No data—
Sun 25 OctSwalmen 21:05No data—
Sat 24 OctSwalmen 21:05No data—
Sun 18 OctSwalmen 21:05+1 min—
Sat 17 OctSwalmen 21:05No data—
Fri 16 OctCuijk 20:06No data—
Sun 11 OctSwalmen 21:050 min—
Sat 10 OctSwalmen 21:040 min—
Sun 4 OctVierlingsbeek 20:21No data—
Sat 3 OctVierlingsbeek 20:22No data—
Sun 27 SeptSwalmen 21:05No data—
Sat 26 SeptSwalmen 21:05No data—
Sun 20 SeptBlerick 20:43No data—
Sat 19 SeptBlerick 20:42No data—
Sun 13 SeptBlerick 20:42No data—
Sat 12 SeptBlerick 20:42No data—
Sun 6 SeptSwalmen 21:04No data—
Sat 5 SeptSwalmen 21:04No data—
Sun 30 AugBlerick 20:42No data—
Sat 29 AugBlerick 20:43No data—