Train Arriva 32265 Nijmegen → Venlo

Nijmegen 18:08 → Venlo 19:01 Daily 0 h 53 min · 9 stops Arriva

Arriva 32265 Nijmegen–Venlo: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Venlo: 19:01. TrainsRadar data as of 22 Nov 2026, 19:06 (GMT+1).

Running now · updated 19:05

Position estimated from the timetable

Heading to Venlo 0 min

Estimated arrival at Venlo 19:01

  1. Nijmegen18:08
  2. Nijmegen Heyendaal18:11
  3. Cuijk18:20
  4. Boxmeer18:29
  5. Vierlingsbeek18:37
  6. Blerick18:58
  7. Venlo19:01

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

On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 16 full · 5 partial · 7 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 22 full · 5 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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:08on time on time
18:11≈ on time ≈ on time
18:16≈ on time ≈ on time
18:20 / 18:22≈ on time ≈ on time
18:29 / 18:32≈ on time ≈ on time
18:37 / 18:38≈ on time ≈ +1 min
18:44 / 18:45≈ on time ≈ +1 min
18:58≈ on time ≈ +1 min
19:01on 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 NovBlerick 19:04Partial coverage0 min—
Sat 21 NovBlerick 19:09Partial coverage0 min—
Fri 20 NovBlerick 19:12Partial coverage0 min—
Thu 19 NovBoxmeer 18:44Partial coverage0 min—
Wed 18 NovVierlingsbeek 18:52Partial coverage0 min—
Tue 17 NovCuijk 18:340 min—
Mon 16 NovCuijk 18:350 min—
Sun 15 NovSwalmen 19:430 min+5 min
Sat 14 NovSwalmen 19:340 min+1 min
Fri 13 NovVenray 18:590 min—
Thu 12 NovCuijk 18:340 min—
Wed 11 NovNijmegen Heyendaal 18:240 min—
Tue 10 NovMook-Molenhoek 18:290 min—
Mon 9 NovNijmegen Heyendaal 18:240 min—
Sun 8 NovSwalmen 19:34+1 min+1 min
Sat 7 NovSwalmen 19:37+2 min+3 min
Fri 6 NovVenray 18:590 min—
Thu 5 NovNijmegen Heyendaal 18:24No data—
Wed 4 NovNijmegen Heyendaal 18:24No data—
Tue 3 NovNijmegen Heyendaal 18:240 min—
Mon 2 NovNijmegen 18:220 min—
Sun 1 NovSwalmen 19:34No data—
Sat 31 OctSwalmen 19:35+1 min—
Fri 30 OctVenray 18:59No data—
Wed 28 OctNijmegen Heyendaal 18:250 min—
Mon 26 OctNijmegen 18:22No data—
Sun 25 OctSwalmen 19:36No data—
Sat 24 OctSwalmen 19:36No data—
Fri 23 OctSwalmen 19:34No data—
Sun 18 OctSwalmen 19:34No data—