Train Arriva 32253 Nijmegen → Venlo

Nijmegen 15:08 → Venlo 16:01 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 15:08 from Nijmegen · Sat 21 Nov

Next departure 15:08 today · Nijmegen
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 15 full · 3 partial · 11 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 25 full · 3 partial · 59 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: +5 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 +7 min · last fix heading to Swalmen +7 min
  • Thu 19 Nov Max en route +6 min · last fix heading to Blerick +6 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Swalmen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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