Train Arriva 32238 Roermond – Nijmegen
✓ Today’s run finished
Today, last fix heading to Nijmegen Heyendaal at 13:02 No data
- Roermond11:34
- Reuver11:44
- Venlo11:57
- Venray12:14
- Boxmeer12:26
- Nijmegen Heyendaal12:48
- Nijmegen12:52
Next service: tomorrow 11:34 from Roermond · Sat 7 Nov
Last 30 days
Arrival delay at Nijmegen, 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 +6 min · last fix heading to Nijmegen Heyendaal +6 min
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 93% · 14
- 3–10 min 7% · 1
- 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
- 0% 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:34 | on time | on time | |
| 11:39 | ≈ on time | ≈ +1 min | |
| 11:44 / 11:45 | ≈ on time | ≈ +1 min | |
| 11:51 | ≈ on time | ≈ +1 min | |
| 11:57 / 11:59 | ≈ on time | ≈ +1 min | |
| 12:01 | ≈ on time | ≈ +1 min | |
| 12:14 / 12:15 | ≈ on time | ≈ +1 min | |
| 12:20 / 12:21 | ≈ on time | ≈ +1 min | |
| 12:26 / 12:30 | ≈ +1 min | ≈ +2 min | |
| 12:37 / 12:38 | ≈ +1 min | ≈ +2 min | |
| 12:42 | ≈ +1 min | ≈ +2 min | |
| 12:48 | ≈ +1 min | ≈ +2 min | |
| 12:52 | +1 min | +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 |
|---|---|---|---|
| Fri 6 Nov | Nijmegen Heyendaal 13:02 | No data | — |
| Thu 5 Nov | Nijmegen Heyendaal 13:03 | No data | — |
| Wed 4 Nov | Nijmegen Heyendaal 13:02Partial coverage | 0 min | — |
| Tue 3 Nov | Nijmegen Heyendaal 12:59 | No data | — |
| Mon 2 Nov | Nijmegen Heyendaal 13:03 | No data | — |
| Sun 1 Nov | Tegelen 12:07 | +1 min | — |
| Sat 31 Oct | Tegelen 12:06 | +1 min | +1 min |
| Fri 30 Oct | Nijmegen Heyendaal 13:03 | No data | — |
| Thu 29 Oct | Nijmegen Heyendaal 13:06 | No data | — |
| Wed 28 Oct | Nijmegen Heyendaal 13:02Partial coverage | 0 min | — |
| Tue 27 Oct | Nijmegen Heyendaal 13:02Partial coverage | 0 min | — |
| Mon 26 Oct | Nijmegen Heyendaal 13:02 | No data | — |
| Sun 25 Oct | Tegelen 12:06 | No data | — |
| Sat 24 Oct | Tegelen 12:06 | 0 min | +1 min |
| Fri 23 Oct | Tegelen 12:07 | No data | — |
| Thu 22 Oct | Tegelen 12:06 | No data | — |
| Wed 21 Oct | Tegelen 12:05 | No data | — |
| Tue 20 Oct | Tegelen 12:06 | 0 min | — |
| Mon 19 Oct | Tegelen 12:07 | No data | — |
| Sun 18 Oct | Tegelen 12:09 | +3 min | +3 min |
| Sat 17 Oct | Tegelen 12:05 | No data | — |
| Fri 16 Oct | Nijmegen Heyendaal 13:03 | No data | — |
| Thu 15 Oct | Nijmegen Heyendaal 13:03 | No data | — |
| Tue 13 Oct | Nijmegen Heyendaal 13:04 | No data | — |
| Mon 12 Oct | Nijmegen Heyendaal 13:03 | No data | — |
| Sun 11 Oct | Nijmegen Heyendaal 13:02Partial coverage | 0 min | — |
| Sat 10 Oct | Nijmegen Heyendaal 13:02Partial coverage | 0 min | — |
| Fri 9 Oct | Nijmegen Heyendaal 13:03Partial coverage | +1 min | — |
| Thu 8 Oct | Nijmegen Heyendaal 13:08Partial coverage | +6 min | +6 min |
| Wed 7 Oct | Nijmegen Heyendaal 13:03Partial coverage | +1 min | — |