Train Arriva 32259 Nijmegen – Venlo

Nijmegen 16:38 → Venlo 17:31 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 18 November +3 min

Next service: today 16:38 from Nijmegen · Thu 19 Nov

Next departure 16:38 today · Nijmegen
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 16 full · 1 partial · 12 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 60 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: +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

  • Thu 12 Nov Max en route +4 min · last fix heading to Swalmen +4 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Swalmen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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