Train NS 6582 Eindhoven Centraal – 's-Hertogenbosch

Eindhoven Centraal 22:35 → 's-Hertogenbosch 23:03 Daily 0 h 28 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 22:35 from Eindhoven Centraal · Fri 6 Nov

Next departure 22:35 today · Eindhoven Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 10 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
22:35on time on time
22:39≈ on time ≈ on time
22:44≈ on time ≈ +1 min
22:51≈ on time ≈ +1 min
22:58≈ on time ≈ +1 min
23:03on time +2 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

DateLast stopFinalMax
Thu 5 Nov— 23:04No data—
Wed 4 Nov— 23:04+1 min—
Tue 3 Nov— 23:050 min—
Mon 2 Nov— 23:04+1 min—
Sun 1 NovVught 23:14+3 min+3 min
Sat 31 OctVught 23:130 min—
Fri 30 Oct— 23:04No data—
Thu 29 Oct— 23:040 min—
Wed 28 Oct— 23:04No data—
Tue 27 Oct— 23:050 min—
Mon 26 Oct— 23:04No data—
Sun 25 OctVught 23:12No data—
Sat 24 OctEindhoven Strijp-S 23:04No data—
Fri 23 Oct— 23:05+1 min+1 min
Thu 22 Oct— 23:070 min—
Wed 21 Oct— 23:05No data—
Mon 19 Oct— 23:04No data—
Sun 18 OctVught 23:13Partial coverage+1 min—
Sat 17 OctVught 23:14No data—
Fri 16 Oct— 23:040 min—
Thu 15 Oct— 23:04No data—
Wed 14 Oct— 23:06+1 min+1 min
Tue 13 Oct— 23:050 min—
Mon 12 Oct— 23:07+1 min+1 min
Sun 11 OctVught 23:12Partial coverage0 min—
Sat 10 Oct— 23:050 min—
Fri 9 Oct— 23:17+6 min+6 min
Thu 8 Oct— 23:040 min—
Wed 7 Oct— 23:040 min—
Tue 6 Oct— 23:00+1 min—