Train NS 6591 's-Hertogenbosch – Eindhoven Centraal

's-Hertogenbosch 00:58 → Eindhoven Centraal 01:26 Daily 0 h 28 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:27 +1 min

  1. 's-Hertogenbosch00:58
  2. Vught01:02
  3. Boxtel01:09
  4. Best01:15
  5. Eindhoven Strijp-S01:22
  6. Eindhoven Centraal01:26

Next service: tomorrow 00:58 from 's-Hertogenbosch · Thu 19 Nov

Next departure 00:58 tomorrow · 's-Hertogenbosch
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 23 full · 0 partial · 3 no data
On-time · 90 days
91%
31/34 runs under 3 min
RT coverage: 34 full · 0 partial · 11 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: +3 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
  • Tue 17 Nov Max en route +3 min · last fix heading to — +3 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 91% · 31
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 83% T n=6
  • 100% W n=7
  • 80% T n=5
  • 100% F n=4
  • 83% S n=6
  • 100% S n=1

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.

StopSched.Usually 9 days in 10
00:58on time on time
01:02≈ on time ≈ on time
01:09≈ on time ≈ on time
01:15≈ on time ≈ on time
01:22≈ on time ≈ on time
01:26on 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
Wed 18 Nov— 01:27+1 min—
Tue 17 Nov— 01:29+3 min+3 min
Mon 16 NovEindhoven Strijp-S 01:240 min—
Sat 14 Nov— 01:380 min—
Fri 13 Nov— 01:320 min—
Thu 12 Nov— 01:320 min—
Wed 11 Nov— 01:290 min—
Tue 10 Nov— 01:270 min—
Mon 9 NovEindhoven Strijp-S 01:220 min—
Sat 7 Nov— 01:290 min—
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—