Train NS 6542 Eindhoven Centraal → 's-Hertogenbosch
NS 6542 Eindhoven Centraal–'s-Hertogenbosch: final delay under 3 min on 21 of its 23 runs with data in the last 30 days (91%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 23:02 (GMT+1).
An alert on this phone or computer when the 6542 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Vught at 13:13 0 min
- Eindhoven Centraal12:35
- Eindhoven Strijp-S12:39
- Best12:44
- Boxtel12:51
- Vught12:58
- 's-Hertogenbosch13:03
Next service: tomorrow 12:35 from Eindhoven Centraal · Mon 23 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 19 Nov Max en route +6 min · last fix heading to Vught +6 min
- Thu 12 Nov Max en route +6 min · last fix heading to Vught +6 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 32
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 100% W n=5
- 60% T n=5
- 100% F n=4
- 100% S n=6
- 100% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 34 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:35 | on time | on time | |
| 12:39 | ≈ on time | ≈ on time | |
| 12:44 | ≈ on time | ≈ +1 min | |
| 12:51 | ≈ on time | ≈ +2 min | |
| 12:58 | ≈ on time | ≈ +2 min | |
| 13: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 |
|---|---|---|---|
| Sun 22 Nov | Vught 13:13Partial coverage | 0 min | — |
| Sat 21 Nov | Vught 13:13 | +1 min | +1 min |
| Fri 20 Nov | Vught 13:14 | +3 min | +4 min |
| Thu 19 Nov | Vught 13:19 | +6 min | +6 min |
| Wed 18 Nov | Vught 13:13 | 0 min | +1 min |
| Tue 17 Nov | Vught 13:12 | 0 min | — |
| Mon 16 Nov | Vught 13:14 | +2 min | +2 min |
| Sun 15 Nov | Vught 13:09Partial coverage | +1 min | +1 min |
| Sat 14 Nov | Vught 13:12 | 0 min | — |
| Fri 13 Nov | Vught 13:14 | +3 min | +3 min |
| Thu 12 Nov | Vught 13:18 | +6 min | +6 min |
| Wed 11 Nov | Vught 13:13 | +1 min | — |
| Tue 10 Nov | Vught 13:12 | 0 min | — |
| Mon 9 Nov | Vught 13:12 | 0 min | — |
| Sun 8 Nov | Vught 13:12Partial coverage | 0 min | — |
| Sat 7 Nov | Vught 13:12 | 0 min | — |
| Fri 6 Nov | Vught 13:13 | No data | — |
| Thu 5 Nov | Vught 13:12 | No data | — |
| Wed 4 Nov | Vught 13:13 | +1 min | — |
| Tue 3 Nov | Vught 13:12 | No data | — |
| Mon 2 Nov | Vught 13:12 | No data | — |
| Sun 1 Nov | Vught 13:14 | 0 min | — |
| Sat 31 Oct | Vught 13:18 | 0 min | — |
| Fri 30 Oct | Vught 13:15Partial coverage | 0 min | — |
| Thu 29 Oct | 's-Hertogenbosch 13:32 | 0 min | — |
| Wed 28 Oct | 's-Hertogenbosch 13:41 | 0 min | — |
| Tue 27 Oct | 's-Hertogenbosch 13:29 | No data | — |
| Mon 26 Oct | 's-Hertogenbosch 13:29 | No data | — |
| Sun 25 Oct | Vught 13:12 | No data | — |
| Sat 24 Oct | Vught 13:12 | 0 min | — |