Train Arriva 32223 Nijmegen – Venlo
✓ Today’s run finished
Today, last fix heading to Blerick at 08:44 +3 min
- Nijmegen07:38
- Nijmegen Heyendaal07:41
- Cuijk07:50
- Boxmeer07:59
- Vierlingsbeek08:07
- Blerick08:28
- Venlo08:31
Next service: tomorrow 07:38 from Nijmegen · Thu 19 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 8 Oct Max en route +13 min · last fix heading to Swalmen +12 min
- Tue 17 Nov Max en route +6 min · last fix heading to Swalmen +5 min
- Sun 18 Oct Max en route +6 min · last fix heading to Swalmen +5 min
- Sat 17 Oct Max en route +5 min · last fix heading to Swalmen +4 min
- Wed 18 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 79% · 19
- 3–10 min 17% · 4
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 80% T n=5
- 80% W n=5
- 50% T n=2
- 100% F n=2
- 75% S n=4
- 67% S n=3
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 07:38 | on time | on time | |
| 07:41 | ≈ on time | ≈ on time | |
| 07:46 | ≈ on time | ≈ +1 min | |
| 07:50 / 07:52 | ≈ on time | ≈ +1 min | |
| 07:59 / 08:02 | ≈ on time | ≈ +2 min | |
| 08:07 / 08:08 | ≈ on time | ≈ +3 min | |
| 08:14 / 08:15 | ≈ on time | ≈ +3 min | |
| 08:28 | ≈ on time | ≈ +5 min | |
| 08:31 | on time | +5 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 |
|---|---|---|---|
| Wed 18 Nov | Blerick 08:44Partial coverage | +3 min | +3 min |
| Tue 17 Nov | Swalmen 09:09 | +5 min | +6 min |
| Mon 16 Nov | Swalmen 09:04 | 0 min | +2 min |
| Sun 15 Nov | Swalmen 09:04 | No data | — |
| Sat 14 Nov | Swalmen 09:04 | +1 min | +1 min |
| Fri 13 Nov | Swalmen 09:04 | 0 min | — |
| Thu 12 Nov | Swalmen 09:04 | 0 min | — |
| Wed 11 Nov | Swalmen 09:04 | 0 min | — |
| Tue 10 Nov | Swalmen 09:04 | 0 min | — |
| Mon 9 Nov | Swalmen 09:04 | 0 min | — |
| Sun 8 Nov | Swalmen 09:04 | 0 min | — |
| Sat 7 Nov | Swalmen 09:04 | 0 min | — |
| Fri 6 Nov | Swalmen 09:04 | No data | — |
| Thu 5 Nov | Swalmen 09:04 | No data | — |
| Wed 4 Nov | Swalmen 09:04 | 0 min | — |
| Tue 3 Nov | Swalmen 09:04 | No data | — |
| Mon 2 Nov | Swalmen 09:04 | No data | — |
| Sun 1 Nov | Swalmen 09:04 | No data | — |
| Sat 31 Oct | Swalmen 09:04 | No data | — |
| Fri 30 Oct | Swalmen 09:07 | No data | — |
| Thu 29 Oct | Swalmen 09:06 | No data | — |
| Wed 28 Oct | Swalmen 09:08 | 0 min | — |
| Tue 27 Oct | Swalmen 09:05 | 0 min | — |
| Mon 26 Oct | Swalmen 09:07 | 0 min | — |
| Sun 25 Oct | Swalmen 09:05 | No data | — |
| Sat 24 Oct | Swalmen 09:05 | No data | — |
| Fri 23 Oct | Swalmen 09:06 | No data | — |
| Thu 22 Oct | Swalmen 09:05 | No data | — |
| Wed 21 Oct | Swalmen 09:04 | No data | — |
| Tue 20 Oct | Swalmen 09:04 | 0 min | — |