Train NS 6534 Eindhoven Centraal – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: today 10:35 from Eindhoven Centraal · Mon 9 Nov

Next departure 10:35 today · Eindhoven Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 16 full · 3 partial · 10 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 21 full · 3 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 +5 min · last fix heading to Vught +5 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 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
10:35on time on time
10:39≈ on time ≈ on time
10:44≈ on time ≈ +1 min
10:51≈ on time ≈ +1 min
10:58≈ on time ≈ +2 min
11:03on 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

DateLast stopFinalMax
Sun 8 NovVught 11:13Partial coverage+2 min+2 min
Sat 7 NovVught 11:120 min—
Fri 6 NovVught 11:14No data—
Thu 5 NovVught 11:13No data—
Wed 4 NovVught 11:13+1 min—
Tue 3 NovVught 11:140 min—
Mon 2 NovVught 11:140 min—
Sun 1 NovVught 11:140 min—
Sat 31 OctVught 11:130 min—
Fri 30 OctVught 11:12No data—
Thu 29 Oct's-Hertogenbosch 11:290 min—
Wed 28 Oct's-Hertogenbosch 11:30No data—
Tue 27 Oct's-Hertogenbosch 11:29No data—
Mon 26 Oct's-Hertogenbosch 11:290 min—
Sun 25 OctVught 11:12No data—
Sat 24 OctVught 11:15+3 min+3 min
Fri 23 OctVught 11:250 min—
Thu 22 OctVught 11:250 min—
Wed 21 OctVught 11:12No data—
Tue 20 OctVught 11:120 min—
Mon 19 OctVught 11:120 min—
Sun 18 OctVught 11:12Partial coverage0 min—
Sat 17 OctVught 11:130 min—
Fri 16 OctVught 11:250 min—
Thu 15 OctVught 11:13No data—
Wed 14 OctVught 11:13No data—
Tue 13 OctVught 11:12No data—
Mon 12 OctVught 11:130 min—
Sun 11 OctVught 11:15Partial coverage+3 min+3 min
Sat 10 OctVught 11:14+3 min+3 min