Train Arriva 32259 Nijmegen → Venlo
Arriva 32259 Nijmegen–Venlo: final delay under 3 min on 18 of its 20 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 00:08 (GMT+1).
An alert on this phone or computer when the 32259 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November 0 min
Next service: today 16:38 from Nijmegen · Sun 22 Nov
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
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 28
- 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
- 67% T n=3
- 67% F n=3
- 100% S n=6
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 30 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 16:38 | on 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:31 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Blerick 17:43Partial coverage | 0 min | — |
| Fri 20 Nov | Blerick 17:44Partial coverage | +2 min | +2 min |
| Thu 19 Nov | Blerick 17:42Partial coverage | +3 min | +3 min |
| Wed 18 Nov | Blerick 17:42Partial coverage | +3 min | +3 min |
| Tue 17 Nov | Swalmen 18:04 | +1 min | +2 min |
| Mon 16 Nov | Swalmen 18:04 | 0 min | — |
| Sun 15 Nov | Swalmen 18:08 | No data | — |
| Sat 14 Nov | Swalmen 18:04 | +1 min | +1 min |
| Fri 13 Nov | Swalmen 18:04 | +3 min | +4 min |
| Thu 12 Nov | Swalmen 18:04 | +4 min | +4 min |
| Wed 11 Nov | Swalmen 18:04 | 0 min | +13 min |
| Tue 10 Nov | Swalmen 18:04 | 0 min | +1 min |
| Mon 9 Nov | Swalmen 18:04 | +1 min | +1 min |
| Sun 8 Nov | Swalmen 18:04 | 0 min | — |
| Sat 7 Nov | Swalmen 18:07 | +2 min | +3 min |
| Fri 6 Nov | Swalmen 18:04 | No data | — |
| Thu 5 Nov | Swalmen 18:04 | No data | — |
| Wed 4 Nov | Swalmen 18:04 | 0 min | — |
| Tue 3 Nov | Swalmen 18:04 | No data | — |
| Mon 2 Nov | Swalmen 18:04 | No data | — |
| Sun 1 Nov | Swalmen 18:05 | 0 min | +1 min |
| Sat 31 Oct | Swalmen 18:05 | 0 min | — |
| Fri 30 Oct | Swalmen 18:04 | No data | — |
| Thu 29 Oct | Swalmen 18:04 | No data | — |
| Wed 28 Oct | Swalmen 18:04 | 0 min | — |
| Tue 27 Oct | Swalmen 18:04 | No data | — |
| Mon 26 Oct | Swalmen 18:04 | 0 min | — |
| Sun 25 Oct | Swalmen 18:04 | No data | — |
| Sat 24 Oct | Swalmen 18:05 | 0 min | — |
| Fri 23 Oct | Swalmen 18:05 | No data | — |