Train Arriva 32235 Nijmegen → Venlo

Nijmegen 10:38 → Venlo 11:31 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Friday 20 November +4 min

Next service: today 10:38 from Nijmegen · Sat 21 Nov

Next departure 10:38 today · Nijmegen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 16 full · 3 partial · 10 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 22 full · 3 partial · 62 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: +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

  • Fri 20 Nov Max en route +5 min · last fix heading to Blerick +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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