Train Arriva 32267 Nijmegen → Venlo
Arriva 32267 Nijmegen–Venlo: final delay under 3 min on 9 of its 10 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 19:54 (GMT+1).
An alert on this phone or computer when the 32267 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Blerick at 19:44 +4 min
- Nijmegen18:38
- Nijmegen Heyendaal18:41
- Cuijk18:50
- Boxmeer18:59
- Vierlingsbeek19:07
- Blerick19:28
- Venlo19:31
Next service: tomorrow 18:38 from Nijmegen · Mon 23 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
- Sun 22 Nov Max en route +4 min · last fix heading to Blerick +4 min
Distribution · 90 days
14 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 13
- 3–10 min 7% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- 100% W n=1
- — T n=0
- 100% F n=3
- 100% S n=4
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 14 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 |
|---|---|---|---|
| 18:38 | on time | on time | |
| 18:41 | ≈ on time | ≈ on time | |
| 18:46 | ≈ on time | ≈ on time | |
| 18:50 / 18:52 | ≈ on time | ≈ on time | |
| 18:59 / 19:02 | ≈ on time | ≈ on time | |
| 19:07 / 19:08 | ≈ on time | ≈ on time | |
| 19:14 / 19:15 | ≈ on time | ≈ on time | |
| 19:28 | ≈ on time | ≈ +1 min | |
| 19:31 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Blerick 19:44Partial coverage | +4 min | +4 min |
| Sat 21 Nov | Blerick 19:42Partial coverage | 0 min | — |
| Fri 20 Nov | Venray 19:29Partial coverage | 0 min | — |
| Wed 18 Nov | Nijmegen Heyendaal 18:53Partial coverage | +2 min | +2 min |
| Sun 15 Nov | Swalmen 20:04 | 0 min | — |
| Sat 14 Nov | Swalmen 20:04 | 0 min | — |
| Fri 13 Nov | Cuijk 19:04 | 0 min | — |
| Sun 8 Nov | Swalmen 20:04 | +1 min | — |
| Sat 7 Nov | Swalmen 20:04 | 0 min | +1 min |
| Fri 6 Nov | Mook-Molenhoek 18:59 | 0 min | — |
| Sun 1 Nov | Swalmen 20:04 | No data | — |
| Sat 31 Oct | Swalmen 20:04 | No data | — |
| Fri 30 Oct | Cuijk 19:06 | No data | — |
| Sun 25 Oct | Swalmen 20:08 | No data | — |
| Sat 24 Oct | Swalmen 20:06 | No data | — |
| Sun 18 Oct | Swalmen 20:06 | +1 min | +1 min |
| Sat 17 Oct | Swalmen 20:04 | No data | — |
| Fri 16 Oct | Swalmen 20:04 | No data | — |
| Tue 13 Oct | Nijmegen 18:50 | No data | — |
| Mon 12 Oct | Nijmegen Heyendaal 18:55 | 0 min | — |
| Sun 11 Oct | Swalmen 20:05 | 0 min | — |
| Sat 10 Oct | Swalmen 20:05 | 0 min | — |
| Sun 4 Oct | Vierlingsbeek 19:22 | No data | — |
| Sat 3 Oct | Vierlingsbeek 19:22 | No data | — |
| Fri 2 Oct | Mook-Molenhoek 19:00 | No data | — |
| Sun 27 Sept | Swalmen 20:05 | No data | — |
| Sat 26 Sept | Swalmen 20:04 | No data | — |
| Sun 20 Sept | Blerick 19:42 | No data | — |
| Sat 19 Sept | Blerick 19:44 | No data | — |
| Fri 18 Sept | Mook-Molenhoek 19:00 | No data | — |