Train NS 3643 Zwolle – Roosendaal
✓ Today’s run finished
Today, last fix heading to Etten-Leur at 15:39 0 min
- Zwolle12:50
- Olst13:06
- Zutphen13:26
- Nijmegen14:05
- 's-Hertogenbosch14:37
- Etten-Leur15:22
- Roosendaal15:33
Next service: tomorrow 12:50 from Zwolle · Thu 12 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
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 100% · 26
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=4
- 100% T n=1
- 100% F n=4
- 100% S n=4
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 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 |
|---|---|---|---|
| 12:50 | on time | on time | |
| 12:59 | ≈ on time | ≈ on time | |
| 13:06 | ≈ on time | ≈ on time | |
| 13:14 / 13:15 | ≈ on time | ≈ on time | |
| 13:26 / 13:28 | ≈ on time | ≈ on time | |
| 13:37 | ≈ on time | ≈ on time | |
| 13:49 / 13:53 | ≈ on time | ≈ on time | |
| 14:05 / 14:09 | ≈ on time | ≈ +1 min | |
| 14:24 / 14:25 | ≈ on time | ≈ +1 min | |
| 14:37 / 14:41 | ≈ on time | ≈ +1 min | |
| 14:56 / 14:58 | ≈ on time | ≈ +1 min | |
| 15:10 / 15:15 | ≈ on time | ≈ +1 min | |
| 15:22 | ≈ on time | ≈ +1 min | |
| 15:33 | 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 |
|---|---|---|---|
| Wed 11 Nov | Etten-Leur 15:39Partial coverage | 0 min | — |
| Tue 10 Nov | Etten-Leur 15:39Partial coverage | 0 min | — |
| Mon 9 Nov | Etten-Leur 15:39Partial coverage | 0 min | — |
| Sun 8 Nov | Oss 14:38 | 0 min | — |
| Sat 7 Nov | Oss 14:38 | +1 min | +1 min |
| Fri 6 Nov | Etten-Leur 15:39 | No data | — |
| Thu 5 Nov | Etten-Leur 15:39 | No data | — |
| Wed 4 Nov | Etten-Leur 15:39Partial coverage | 0 min | — |
| Tue 3 Nov | Etten-Leur 15:39 | No data | — |
| Mon 2 Nov | Etten-Leur 15:44Partial coverage | 0 min | — |
| Sun 1 Nov | Etten-Leur 15:41 | +2 min | +2 min |
| Sat 31 Oct | Etten-Leur 15:40 | +1 min | +1 min |
| Fri 30 Oct | Etten-Leur 15:39 | 0 min | — |
| Thu 29 Oct | Etten-Leur 15:39 | No data | — |
| Wed 28 Oct | Etten-Leur 15:58 | 0 min | — |
| Tue 27 Oct | Etten-Leur 15:39 | 0 min | — |
| Mon 26 Oct | Etten-Leur 15:39 | No data | — |
| Fri 23 Oct | Etten-Leur 15:45 | 0 min | — |
| Thu 22 Oct | Etten-Leur 15:40 | No data | — |
| Wed 21 Oct | Etten-Leur 15:40 | No data | — |
| Tue 20 Oct | Etten-Leur 15:40 | 0 min | — |
| Mon 19 Oct | Etten-Leur 15:40Partial coverage | 0 min | — |
| Sun 18 Oct | Etten-Leur 15:39 | 0 min | — |
| Sat 17 Oct | Etten-Leur 15:40 | 0 min | — |
| Fri 16 Oct | Etten-Leur 15:39 | 0 min | — |
| Thu 15 Oct | Etten-Leur 15:39 | No data | — |
| Wed 14 Oct | Etten-Leur 15:39 | No data | — |
| Tue 13 Oct | Etten-Leur 15:39 | No data | — |
| Mon 12 Oct | Etten-Leur 15:39Partial coverage | 0 min | — |
| Sun 11 Oct | Etten-Leur 15:39 | 0 min | — |