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