Train NS 3648 Roosendaal – Zwolle
It has not run yet today
Last recorded run: Wednesday 11 November +9 min
Next service: today 14:57 from Roosendaal · Thu 12 Nov
Last 30 days
Arrival delay at Zwolle, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 11 Nov Max en route +10 min · last fix heading to Wijhe +9 min
- Tue 10 Nov Max en route +8 min · last fix heading to Wijhe +7 min
- Sat 10 Oct Max en route +4 min · last fix heading to Wijhe +4 min
- Sun 1 Nov Max en route +5 min · last fix heading to Wijhe +4 min
- Thu 8 Oct Max en route +4 min · last fix heading to Wijhe +4 min
Distribution · 90 days
25 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 76% · 19
- 3–10 min 24% · 6
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 67% T n=3
- 75% W n=4
- 50% T n=2
- 100% F n=4
- 67% S n=3
- 50% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 25 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 |
|---|---|---|---|
| 14:57 | on time | on time | |
| 15:07 | ≈ on time | ≈ on time | |
| 15:15 / 15:19 | ≈ on time | ≈ on time | |
| 15:32 / 15:34 | ≈ on time | ≈ +1 min | |
| 15:50 / 15:54 | ≈ on time | ≈ +1 min | |
| 16:05 | ≈ on time | ≈ +1 min | |
| 16:22 / 16:24 | ≈ on time | ≈ +2 min | |
| 16:37 / 16:41 | ≈ on time | ≈ +2 min | |
| 16:52 / 16:53 | ≈ on time | ≈ +3 min | |
| 17:02 / 17:03 | ≈ on time | ≈ +3 min | |
| 17:15 / 17:16 | ≈ on time | ≈ +3 min | |
| 17:23 | ≈ on time | ≈ +3 min | |
| 17:29 | ≈ on time | ≈ +3 min | |
| 17:40 | on time | +4 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 11 Nov | Wijhe 17:52Partial coverage | +9 min | +10 min |
| Tue 10 Nov | Wijhe 17:48Partial coverage | +7 min | +8 min |
| Mon 9 Nov | Wijhe 17:44Partial coverage | 0 min | +1 min |
| Sun 8 Nov | Wijhe 17:48 | +2 min | +3 min |
| Sat 7 Nov | Wijhe 17:44 | 0 min | +1 min |
| Fri 6 Nov | Wijhe 17:44 | 0 min | +2 min |
| Thu 5 Nov | Wijhe 18:04Partial coverage | 0 min | — |
| Wed 4 Nov | Wijhe 17:44Partial coverage | 0 min | — |
| Tue 3 Nov | Wijhe 17:43 | No data | — |
| Mon 2 Nov | Wijhe 18:17 | No data | — |
| Sun 1 Nov | Wijhe 17:48 | +4 min | +5 min |
| Sat 31 Oct | Wijhe 17:44 | +1 min | — |
| Fri 30 Oct | Wijhe 17:44 | No data | — |
| Thu 29 Oct | Arnhem Zuid 16:52 | No data | — |
| Wed 28 Oct | Arnhem Zuid 16:48 | 0 min | — |
| Tue 27 Oct | Arnhem Zuid 16:52 | No data | — |
| Mon 26 Oct | Arnhem Zuid 16:54 | 0 min | — |
| Fri 23 Oct | Nijmegen 16:50 | 0 min | — |
| Thu 22 Oct | Nijmegen 16:41 | No data | — |
| Wed 21 Oct | Nijmegen 16:49 | No data | — |
| Tue 20 Oct | Nijmegen 16:41 | 0 min | — |
| Mon 19 Oct | Wijhe 17:43Partial coverage | 0 min | — |
| Sun 18 Oct | Wijhe 17:47 | +3 min | +4 min |
| Sat 17 Oct | Wijhe 17:44 | No data | — |
| Fri 16 Oct | Wijhe 17:47 | 0 min | — |
| Thu 15 Oct | Wijhe 17:44 | No data | — |
| Wed 14 Oct | Wijhe 17:44 | No data | — |
| Tue 13 Oct | Wijhe 17:44 | No data | — |
| Mon 12 Oct | Wijhe 17:44 | 0 min | — |
| Sun 11 Oct | Wijhe 17:46 | +1 min | +2 min |