Train Arriva 32245 Nijmegen – Venlo

Nijmegen 13:08 → Venlo 14:00 Daily 0 h 52 min · 9 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 13:08 from Nijmegen · Mon 16 Nov

Next departure 13:08 today · Nijmegen
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 16 full · 1 partial · 12 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 23 full · 1 partial · 63 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: +4 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 +8 min · last fix heading to Swalmen +7 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Swalmen +6 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Blerick +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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