Train NS 6528 Deurne – 's-Hertogenbosch
✓ Today’s run finished
Today, last fix heading to Vught at 09:42 0 min
- Deurne08:37
- Helmond08:46
- Helmond 't Hout08:49
- Eindhoven Centraal08:59
- Best09:14
- Vught09:28
- 's-Hertogenbosch09:33
Next service: tomorrow 08:37 from Deurne · Mon 9 Nov
Last 30 days
Arrival delay at 's-Hertogenbosch, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 9 Oct Max en route +5 min · last fix heading to Vught +5 min
- Sun 1 Nov Max en route +4 min · last fix heading to Vught +4 min
- Sun 11 Oct Max en route +4 min · last fix heading to Vught +4 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 88% · 21
- 3–10 min 13% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=4
- 100% W n=3
- 100% T n=4
- 0% F n=1
- 100% S n=5
- 50% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 24 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 |
|---|---|---|---|
| 08:37 | on time | on time | |
| 08:42 | ≈ on time | ≈ on time | |
| 08:46 | ≈ on time | ≈ on time | |
| 08:49 | ≈ on time | ≈ on time | |
| 08:51 | ≈ on time | ≈ on time | |
| 08:59 / 09:05 | ≈ on time | ≈ on time | |
| 09:09 | ≈ on time | ≈ on time | |
| 09:14 | ≈ on time | ≈ on time | |
| 09:21 | ≈ on time | ≈ on time | |
| 09:28 | ≈ on time | ≈ on time | |
| 09:33 | on time | on time |
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 |
|---|---|---|---|
| Sun 8 Nov | Vught 09:42Partial coverage | 0 min | — |
| Sat 7 Nov | Vught 09:43Partial coverage | +3 min | +3 min |
| Fri 6 Nov | Vught 09:54 | No data | — |
| Thu 5 Nov | Vught 09:44 | 0 min | — |
| Wed 4 Nov | Vught 09:42 | 0 min | — |
| Tue 3 Nov | Vught 09:49 | 0 min | — |
| Mon 2 Nov | Vught 09:43 | 0 min | — |
| Sun 1 Nov | Vught 09:47 | +4 min | +4 min |
| Sat 31 Oct | Vught 09:43 | +1 min | +1 min |
| Fri 30 Oct | Vught 09:42 | No data | — |
| Thu 29 Oct | 's-Hertogenbosch 09:59 | 0 min | — |
| Wed 28 Oct | 's-Hertogenbosch 09:59 | No data | — |
| Tue 27 Oct | 's-Hertogenbosch 09:58 | 0 min | — |
| Mon 26 Oct | 's-Hertogenbosch 10:01 | 0 min | — |
| Sun 25 Oct | Vught 09:42 | No data | — |
| Sat 24 Oct | Vught 09:43 | 0 min | — |
| Fri 23 Oct | Vught 09:45 | No data | — |
| Thu 22 Oct | Vught 09:45 | 0 min | — |
| Wed 21 Oct | Vught 09:42 | 0 min | — |
| Tue 20 Oct | Vught 09:42 | 0 min | — |
| Mon 19 Oct | Vught 09:43 | 0 min | — |
| Sun 18 Oct | Vught 09:42Partial coverage | 0 min | — |
| Sat 17 Oct | Vught 09:43Partial coverage | +1 min | — |
| Fri 16 Oct | Vught 09:42 | No data | — |
| Thu 15 Oct | Vught 10:58 | No data | — |
| Wed 14 Oct | Vught 09:42 | No data | — |
| Tue 13 Oct | Vught 09:43 | No data | — |
| Mon 12 Oct | Vught 09:43 | No data | — |
| Sun 11 Oct | Vught 09:46Partial coverage | +4 min | +4 min |
| Sat 10 Oct | Vught 09:43Partial coverage | 0 min | — |