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