Train Arriva 32251 Nijmegen → Venlo

Nijmegen 14:38 → Venlo 15:31 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Friday 20 November 0 min

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

Next departure 14:38 today · Nijmegen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 13 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 23 full · 3 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 11 Nov Max en route +4 min · last fix heading to Swalmen +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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