Train Arriva 32225 Nijmegen → Venlo

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

Arriva 32225 Nijmegen–Venlo: final delay under 3 min on 18 of its 19 runs with data in the last 30 days (95%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 01:14 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 08:08 from Nijmegen · Sun 22 Nov

Next departure 08:08 today · Nijmegen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 10 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 23 full · 4 partial · 60 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

Worst days

  • Sun 18 Oct Max en route +8 min · last fix heading to Swalmen +7 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Swalmen +4 min
  • Thu 19 Nov Max en route +4 min · last fix heading to Blerick +4 min

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 89% · 24
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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 10
08:08on time on time
08:11≈ on time ≈ on time
08:16≈ on time ≈ on time
08:20 / 08:22≈ on time ≈ on time
08:29 / 08:32≈ on time ≈ +1 min
08:37 / 08:38≈ on time ≈ +1 min
08:44 / 08:45≈ on time ≈ +1 min
08:58≈ +1 min ≈ +1 min
09:01+1 min +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
Sat 21 NovBlerick 09:12Partial coverage0 min—
Fri 20 NovBlerick 09:13Partial coverage0 min—
Thu 19 NovBlerick 09:14Partial coverage+4 min+4 min
Wed 18 NovBlerick 09:14Partial coverage+2 min+2 min
Tue 17 NovSwalmen 09:34+1 min+2 min
Mon 16 NovSwalmen 09:34+1 min+1 min
Sun 15 NovSwalmen 09:34No data—
Sat 14 NovSwalmen 09:34+1 min+1 min
Fri 13 NovSwalmen 09:34+1 min+2 min
Thu 12 NovSwalmen 09:340 min+1 min
Wed 11 NovSwalmen 09:34+1 min+2 min
Tue 10 NovSwalmen 09:34+1 min—
Mon 9 NovSwalmen 09:34+1 min+2 min
Sun 8 NovSwalmen 09:340 min—
Sat 7 NovSwalmen 09:340 min+1 min
Fri 6 NovSwalmen 09:34No data—
Thu 5 NovSwalmen 09:34No data—
Wed 4 NovSwalmen 09:34+1 min—
Tue 3 NovSwalmen 09:34No data—
Mon 2 NovSwalmen 09:34No data—
Sun 1 NovSwalmen 09:34No data—
Sat 31 OctSwalmen 09:36+1 min+2 min
Fri 30 OctSwalmen 09:36No data—
Thu 29 OctSwalmen 09:35No data—
Wed 28 OctSwalmen 09:360 min—
Tue 27 OctTegelen 09:440 min—
Mon 26 OctSwalmen 09:35No data—
Sun 25 OctSwalmen 09:35No data—
Sat 24 OctSwalmen 09:340 min—
Fri 23 OctSwalmen 09:35No data—