Train Arriva 32227 Nijmegen – Roermond
✓ Today’s run finished
Today, last fix heading to Swalmen at 10:04 No data
- Nijmegen08:38
- Mook-Molenhoek08:46
- Boxmeer08:59
- Venray09:14
- Venlo09:31
- Swalmen09:50
- Roermond09:56
Next service: tomorrow 08:38 from Nijmegen · Sat 7 Nov
Last 30 days
Arrival delay at Roermond, 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 11 Oct Max en route +6 min · last fix heading to Swalmen +6 min
- Sun 18 Oct Max en route +6 min · last fix heading to Swalmen +5 min
Distribution · 90 days
12 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 10
- 3–10 min 17% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 100% T n=3
- 100% W n=3
- 100% T n=1
- 100% F n=1
- 100% S n=2
- 0% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 12 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 |
|---|---|---|---|
| 08:38 | on time | on time | |
| 08:41 | — | — | |
| 08:46 | — | — | |
| 08:50 / 08:52 | — | — | |
| 08:59 / 09:02 | — | — | |
| 09:07 / 09:08 | — | — | |
| 09:14 / 09:15 | — | — | |
| 09:28 | — | — | |
| 09:31 / 09:33 | — | — | |
| 09:38 | — | — | |
| 09:44 / 09:45 | — | — | |
| 09:50 | — | — | |
| 09:56 | — | — |
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 |
|---|---|---|---|
| Fri 6 Nov | Swalmen 10:04 | No data | — |
| Thu 5 Nov | Swalmen 10:04 | No data | — |
| Wed 4 Nov | Swalmen 10:04Partial coverage | 0 min | — |
| Tue 3 Nov | Swalmen 10:07 | No data | — |
| Mon 2 Nov | Swalmen 10:04 | No data | — |
| Sun 1 Nov | Swalmen 10:04 | No data | — |
| Sat 31 Oct | Swalmen 10:04 | No data | — |
| Fri 30 Oct | Swalmen 10:04 | No data | — |
| Thu 29 Oct | Swalmen 10:05 | No data | — |
| Wed 28 Oct | Swalmen 10:10Partial coverage | 0 min | — |
| Tue 27 Oct | Swalmen 10:06Partial coverage | 0 min | — |
| Mon 26 Oct | Swalmen 10:04 | No data | — |
| Sun 25 Oct | Swalmen 10:05 | No data | — |
| Sat 24 Oct | Swalmen 10:04 | No data | — |
| Fri 23 Oct | Swalmen 10:04 | No data | — |
| Thu 22 Oct | Swalmen 10:08 | No data | — |
| Wed 21 Oct | Swalmen 10:04 | No data | — |
| Tue 20 Oct | Swalmen 10:04 | 0 min | — |
| Mon 19 Oct | Swalmen 10:04 | No data | — |
| Sun 18 Oct | Swalmen 10:10 | +5 min | +6 min |
| Sat 17 Oct | Swalmen 10:05 | +1 min | — |
| Fri 16 Oct | Swalmen 10:07 | No data | — |
| Thu 15 Oct | Swalmen 10:08 | No data | — |
| Tue 13 Oct | Swalmen 10:04 | No data | — |
| Mon 12 Oct | Swalmen 10:07 | No data | — |
| Sun 11 Oct | Swalmen 10:08Partial coverage | +6 min | +6 min |
| Sat 10 Oct | Swalmen 10:05Partial coverage | 0 min | — |
| Fri 9 Oct | Swalmen 10:05Partial coverage | 0 min | — |
| Thu 8 Oct | Swalmen 10:06Partial coverage | +1 min | +2 min |
| Wed 7 Oct | Swalmen 10:09Partial coverage | 0 min | +2 min |