Train NS 6538 Deurne – 's-Hertogenbosch
✓ Today’s run finished
Today, last fix heading to Vught at 12:12 No data
- Deurne11:07
- Helmond11:16
- Helmond 't Hout11:19
- Eindhoven Centraal11:29
- Best11:44
- Vught11:58
- 's-Hertogenbosch12:03
Next service: tomorrow 11:07 from Deurne · Sat 7 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
- Thu 8 Oct Max en route +9 min · last fix heading to Vught +9 min
- Sun 18 Oct Max en route +5 min · last fix heading to Vught +5 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 16
- 3–10 min 11% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=3
- 100% W n=4
- 50% T n=2
- 100% F n=1
- 100% S n=4
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 18 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:07 | on time | on time | |
| 11:12 | ≈ on time | ≈ on time | |
| 11:16 | ≈ on time | ≈ +1 min | |
| 11:19 | ≈ on time | ≈ +1 min | |
| 11:21 | ≈ on time | ≈ +1 min | |
| 11:29 / 11:35 | ≈ on time | ≈ +1 min | |
| 11:39 | ≈ on time | ≈ +2 min | |
| 11:44 | ≈ on time | ≈ +2 min | |
| 11:51 | ≈ on time | ≈ +2 min | |
| 11:58 | ≈ on time | ≈ +3 min | |
| 12:03 | 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 | Vught 12:12 | No data | — |
| Thu 5 Nov | Vught 12:13Partial coverage | 0 min | — |
| Wed 4 Nov | Vught 12:12Partial coverage | 0 min | — |
| Tue 3 Nov | Vught 12:13 | No data | — |
| Mon 2 Nov | Vught 12:14 | No data | — |
| Sun 1 Nov | Vught 12:14 | 0 min | — |
| Sat 31 Oct | Vught 12:13 | 0 min | — |
| Fri 30 Oct | Vught 12:12 | No data | — |
| Thu 29 Oct | 's-Hertogenbosch 12:29 | No data | — |
| Wed 28 Oct | 's-Hertogenbosch 12:29 | 0 min | — |
| Tue 27 Oct | 's-Hertogenbosch 12:30 | 0 min | — |
| Mon 26 Oct | 's-Hertogenbosch 12:29 | No data | — |
| Sun 25 Oct | Vught 12:13 | No data | — |
| Sat 24 Oct | Vught 12:12Partial coverage | 0 min | — |
| Fri 23 Oct | Vught 12:12 | No data | — |
| Thu 22 Oct | Vught 12:12 | No data | — |
| Wed 21 Oct | Vught 12:12Partial coverage | 0 min | — |
| Tue 20 Oct | Vught 12:13Partial coverage | 0 min | — |
| Mon 19 Oct | Vught 12:12Partial coverage | 0 min | — |
| Sun 18 Oct | Vught 12:17 | +5 min | +5 min |
| Sat 17 Oct | Vught 12:12 | 0 min | — |
| Fri 16 Oct | Vught 12:12 | No data | — |
| Thu 15 Oct | Vught 12:13 | No data | — |
| Wed 14 Oct | Vught 12:12 | No data | — |
| Tue 13 Oct | Vught 12:12 | No data | — |
| Mon 12 Oct | Vught 12:12 | No data | — |
| Sun 11 Oct | Vught 12:13 | 0 min | — |
| Sat 10 Oct | Vught 12:12 | +3 min | +3 min |
| Fri 9 Oct | Vught 12:12 | +2 min | +2 min |
| Thu 8 Oct | Vught 12:21Partial coverage | +9 min | +9 min |