Train NS 6512 Eindhoven Centraal – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Vught at 05:43 0 min

  1. Eindhoven Centraal05:05
  2. Eindhoven Strijp-S05:09
  3. Best05:14
  4. Boxtel05:22
  5. Vught05:29
  6. 's-Hertogenbosch05:34

Next service: tomorrow 05:05 from Eindhoven Centraal · Wed 18 Nov

Next departure 05:05 tomorrow · Eindhoven Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 19 full · 1 partial · 2 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 28 full · 1 partial · 34 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: +1 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 +3 min · last fix heading to Vught +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
05:05on time on time
05:09≈ on time ≈ on time
05:14≈ on time ≈ on time
05:22≈ on time ≈ +1 min
05:29≈ on time ≈ +1 min
05:34on 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
Tue 17 NovVught 05:43Partial coverage0 min—
Mon 16 NovEindhoven Centraal 06:480 min+34 min
Fri 13 NovVught 05:43+1 min+1 min
Thu 12 NovVught 05:420 min—
Wed 11 NovVught 05:44+1 min—
Tue 10 NovVught 05:430 min—
Mon 9 NovVught 05:480 min—
Fri 6 NovVught 05:42No data—
Thu 5 NovVught 05:43+1 min+1 min
Wed 4 NovVught 05:430 min—
Tue 3 NovVught 05:430 min—
Mon 2 NovVught 05:49No data—
Fri 30 OctVught 05:43+1 min+1 min
Thu 29 OctVught 05:420 min—
Wed 28 OctVught 05:44+1 min—
Tue 27 OctVught 05:430 min—
Mon 26 OctVught 05:52+1 min+1 min
Fri 23 OctVught 05:43+1 min+1 min
Thu 22 OctVught 05:420 min—
Wed 21 OctVught 05:430 min—
Tue 20 OctVught 05:430 min—
Mon 19 OctVught 05:49+1 min+1 min
Fri 16 OctVught 05:420 min—
Thu 15 OctVught 05:420 min—
Wed 14 OctVught 05:44+1 min+1 min
Tue 13 OctVught 05:430 min—
Mon 12 OctVught 05:49+1 min+1 min
Fri 9 OctVught 05:45+3 min+3 min
Thu 8 OctVught 05:420 min—
Wed 7 OctVught 05:430 min—