Train NS 6591 's-Hertogenbosch – Eindhoven Centraal

's-Hertogenbosch 01:03 → Eindhoven Centraal 01:30 Daily 0 h 27 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:29 No data

  1. 's-Hertogenbosch01:03
  2. Vught01:07
  3. Boxtel01:14
  4. Best01:20
  5. Eindhoven Strijp-S01:26
  6. Eindhoven Centraal01:30

Next service: tomorrow 01:03 from 's-Hertogenbosch · Sat 7 Nov

Next departure 01:03 tomorrow · 's-Hertogenbosch
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 5 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Eindhoven Centraal, 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 5 Nov Max en route +26 min · last fix heading to — +26 min
  • Sat 24 Oct Max en route +4 min · last fix heading to — +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 92% · 22
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=5
  • 75% T n=4
  • 100% F n=3
  • 75% S n=4
  • 100% S n=1

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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.

StopSched.Usually 9 days in 10
01:03on time on time
01:07≈ on time ≈ on time
01:14≈ on time ≈ on time
01:20≈ on time ≈ on time
01:26≈ on time ≈ on time
01:30on 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

DateLast stopFinalMax
Fri 6 Nov— 01:29No data—
Thu 5 Nov— 02:24+26 min+26 min
Wed 4 Nov— 01:280 min—
Tue 3 Nov— 01:240 min—
Mon 2 NovEindhoven Strijp-S 01:540 min—
Sat 31 Oct— 01:480 min—
Fri 30 Oct— 01:380 min—
Thu 29 Oct— 01:310 min—
Wed 28 Oct— 01:280 min—
Tue 27 Oct— 01:250 min—
Mon 26 OctEindhoven Strijp-S 01:23No data—
Sun 25 Oct— 01:36No data—
Sat 24 Oct— 01:31+4 min+4 min
Fri 23 Oct— 01:400 min—
Thu 22 Oct— 01:310 min—
Wed 21 Oct— 01:260 min—
Mon 19 OctEindhoven Strijp-S 01:210 min—
Sun 18 OctEindhoven Strijp-S 01:40No data—
Sat 17 Oct— 01:310 min—
Fri 16 Oct— 01:31No data—
Thu 15 Oct— 01:320 min—
Wed 14 Oct— 01:320 min—
Tue 13 Oct— 01:260 min—
Mon 12 OctEindhoven Strijp-S 01:220 min—
Sun 11 Oct— 01:320 min—
Sat 10 Oct— 01:310 min—
Fri 9 Oct— 01:310 min—
Wed 7 Oct— 01:270 min—
Tue 6 Oct— 01:260 min—
Mon 5 OctEindhoven Strijp-S 01:22No data—