Train NS 3663 Zwolle – Roosendaal
✓ Today’s run finished
Today, last fix heading to Dieren at 20:34 +1 min
- Zwolle17:50
- Olst18:06
- Zutphen18:26
- Dieren18:37
- Arnhem Centraal18:49
- Nijmegen19:05
- Roosendaal20:33
Next service: tomorrow 17:50 from Zwolle · Sat 7 Nov
Last 30 days
Arrival delay at Roosendaal, 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 +15 min · last fix heading to Wijhe +15 min
- Fri 9 Oct Max en route +10 min · last fix heading to Zutphen +10 min
- Wed 7 Oct Max en route +4 min · last fix heading to Olst +3 min
Distribution · 90 days
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 18
- 3–10 min 10% · 2
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=1
- 67% W n=3
- 67% T n=3
- 80% F n=5
- 100% S n=2
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 21 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 |
|---|---|---|---|
| 17:50 | on time | on time | |
| 17:59 | ≈ on time | ≈ on time | |
| 18:06 | ≈ on time | ≈ on time | |
| 18:14 / 18:15 | ≈ on time | ≈ on time | |
| 18:26 / 18:28 | ≈ on time | ≈ +1 min | |
| 18:37 | ≈ on time | ≈ +1 min | |
| 18:49 / 18:53 | ≈ on time | ≈ +1 min | |
| 19:05 / 19:08 | ≈ on time | ≈ +1 min | |
| 19:23 / 19:24 | ≈ on time | ≈ +2 min | |
| 19:36 / 19:41 | ≈ on time | ≈ +2 min | |
| 19:57 / 19:58 | ≈ on time | ≈ +2 min | |
| 20:11 / 20:15 | ≈ on time | ≈ +3 min | |
| 20:22 | ≈ on time | ≈ +3 min | |
| 20:33 | on time | +3 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 | Dieren 20:34Partial coverage | +1 min | +3 min |
| Thu 5 Nov | Olst 19:38 | 0 min | — |
| Wed 4 Nov | Deventer 20:34 | 0 min | — |
| Tue 3 Nov | Olst 20:35 | No data | — |
| Mon 2 Nov | Olst 20:54 | 0 min | — |
| Sun 1 Nov | Etten-Leur 20:39 | 0 min | — |
| Sat 31 Oct | Etten-Leur 20:40 | +3 min | +3 min |
| Fri 30 Oct | Arnhem Centraal 20:34 | 0 min | — |
| Thu 29 Oct | — 20:34 | 0 min | — |
| Wed 28 Oct | — 20:34 | 0 min | — |
| Tue 27 Oct | — 20:02 | No data | — |
| Mon 26 Oct | — 20:34 | No data | — |
| Fri 23 Oct | Oss 20:34 | 0 min | — |
| Thu 22 Oct | — 20:35 | No data | — |
| Wed 21 Oct | — 20:35 | No data | — |
| Tue 20 Oct | — 20:34 | No data | — |
| Mon 19 Oct | Dieren 19:26 | 0 min | — |
| Sun 18 Oct | Etten-Leur 20:41 | 0 min | — |
| Sat 17 Oct | Etten-Leur 20:40 | No data | — |
| Fri 16 Oct | 's-Hertogenbosch 20:34Partial coverage | 0 min | — |
| Thu 15 Oct | Zutphen 20:11 | No data | — |
| Wed 14 Oct | 's-Hertogenbosch 20:35 | No data | — |
| Tue 13 Oct | Dieren 20:35 | No data | — |
| Mon 12 Oct | Dieren 20:34 | 0 min | — |
| Sun 11 Oct | Etten-Leur 20:41 | +1 min | +1 min |
| Sat 10 Oct | Etten-Leur 20:40 | 0 min | — |
| Fri 9 Oct | Zutphen 20:53Partial coverage | +10 min | +10 min |
| Thu 8 Oct | Wijhe 19:36 | +15 min | +15 min |
| Wed 7 Oct | Olst 20:53 | +3 min | +4 min |
| Tue 6 Oct | Wijhe 20:37 | +3 min | +3 min |