Train NS 6514 Eindhoven Centraal – 's-Hertogenbosch

Eindhoven Centraal 05:35 → 's-Hertogenbosch 06:03 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 6 stops NS (Nederlandse Spoorwegen)

Running now · updated 05:37

Heading to 's-Hertogenbosch 0 min

Estimated arrival at 's-Hertogenbosch 06:03 · 59 km/h

  1. Eindhoven Centraal05:35
  2. Eindhoven Strijp-S05:39
  3. Best05:44
  4. Boxtel05:51
  5. Vught05:58
  6. 's-Hertogenbosch06:03

Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 20 runs arrived on time.

On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 6 full · 14 partial · 2 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 6 full · 26 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Wed 18 Nov Max en route +11 min · last fix heading to Vught +11 min
  • Thu 5 Nov Max en route +3 min · last fix heading to Vught +3 min
  • Mon 19 Oct Max en route +3 min · last fix heading to Vught +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=7
  • 86% W n=7
  • 86% T n=7
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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 10Today
05:35on time on time
05:39≈ on time ≈ on time
05:44≈ on time ≈ on time
05:51≈ on time ≈ on time
05:58≈ on time ≈ on time
06:03on time +1 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
Fri 20 NovEindhoven Centraal 05:34Partial coverage0 min—
Thu 19 NovVught 06:13Partial coverage0 min—
Wed 18 NovVught 06:24Partial coverage+11 min+11 min
Tue 17 NovVught 06:13Partial coverage+1 min+1 min
Mon 16 NovVught 06:13Partial coverage+1 min+1 min
Fri 13 NovVught 06:12Partial coverage0 min—
Thu 12 NovVught 06:13Partial coverage0 min—
Wed 11 NovVught 06:13Partial coverage+1 min+1 min
Tue 10 NovVught 06:12Partial coverage0 min—
Mon 9 NovVught 06:12Partial coverage0 min—
Fri 6 NovVught 06:14No data—
Thu 5 NovVught 06:14Partial coverage+3 min+3 min
Wed 4 NovVught 06:14Partial coverage+2 min+3 min
Tue 3 NovVught 06:130 min—
Mon 2 NovVught 06:14No data—
Fri 30 OctVught 06:12Partial coverage0 min—
Thu 29 Oct's-Hertogenbosch 06:290 min—
Wed 28 Oct's-Hertogenbosch 06:290 min—
Tue 27 Oct's-Hertogenbosch 06:30+1 min+1 min
Mon 26 Oct's-Hertogenbosch 06:290 min—
Fri 23 OctVught 06:120 min—
Thu 22 OctVught 06:13Partial coverage+1 min+2 min
Wed 21 OctVught 06:12Partial coverage0 min—
Tue 20 OctVught 06:12Partial coverage0 min—
Mon 19 OctVught 06:15Partial coverage+3 min+3 min
Fri 16 OctVught 06:12Partial coverage0 min—
Thu 15 OctVught 06:12Partial coverage0 min—
Wed 14 OctVught 06:12Partial coverage0 min—
Tue 13 OctVught 06:13Partial coverage+1 min+1 min
Mon 12 OctVught 06:25Partial coverage+1 min+1 min