Train Arriva 32231 Nijmegen – Venlo

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

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 09:38 from Nijmegen · Wed 18 Nov

Next departure 09:38 today · Nijmegen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 5 full · 11 partial · 13 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 9 full · 14 partial · 64 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Mon 16 Nov Max en route +3 min · last fix heading to Blerick +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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