Train NS 6546 Eindhoven Centraal – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Vught at 14:13 +1 min

  1. Eindhoven Centraal13:35
  2. Eindhoven Strijp-S13:39
  3. Best13:44
  4. Boxtel13:51
  5. Vught13:58
  6. 's-Hertogenbosch14:03

Next service: tomorrow 13:35 from Eindhoven Centraal · Mon 9 Nov

Next departure 13:35 tomorrow · Eindhoven Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 14 full · 3 partial · 13 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 66 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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