Train NS 6587 's-Hertogenbosch – Eindhoven Centraal

's-Hertogenbosch 23:58 → Eindhoven Centraal 00:25 Daily 0 h 27 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 23:58 from 's-Hertogenbosch · Sat 7 Nov

Next departure 23:58 today · 's-Hertogenbosch
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 4 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 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

Distribution · 90 days

25 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 100% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 stops).

Last 90 days, 25 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
23:58on time on time
00:03≈ on time ≈ on time
00:09≈ on time ≈ on time
00:16≈ on time ≈ on time
00:22≈ on time ≈ on time
00:25on 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— 00:440 min—
Thu 5 Nov— 00:27No data—
Wed 4 Nov— 00:29+2 min+2 min
Tue 3 Nov— 00:290 min—
Sun 1 NovEindhoven Strijp-S 00:340 min—
Sat 31 Oct— 01:130 min—
Fri 30 Oct— 01:120 min—
Thu 29 Oct— 00:270 min—
Wed 28 Oct— 00:260 min—
Mon 26 Oct— 00:320 min—
Sun 25 OctHelmond Brouwhuis 01:02No data—
Sat 24 Oct— 00:270 min+4 min
Thu 22 Oct— 00:260 min—
Wed 21 Oct— 00:310 min—
Tue 20 Oct— 00:310 min—
Mon 19 Oct— 00:260 min—
Sun 18 OctHelmond Brouwhuis 01:020 min—
Sat 17 OctEindhoven Strijp-S 01:15No data—
Fri 16 Oct— 00:440 min—
Thu 15 Oct— 00:290 min—
Wed 14 Oct— 00:260 min—
Tue 13 Oct— 00:31No data—
Mon 12 Oct— 00:260 min—
Sun 11 OctHelmond 't Hout 01:110 min—
Sat 10 Oct— 01:270 min—
Fri 9 Oct— 01:130 min—
Thu 8 Oct— 00:260 min—
Wed 7 Oct— 00:260 min—
Mon 5 OctBoxtel 00:260 min—
Sun 4 OctHelmond Brouwhuis 01:04No data—