Train NS 6542 Eindhoven Centraal – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

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

Next departure 12:35 today · Eindhoven Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 10 full · 4 partial · 15 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 16 full · 4 partial · 67 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: 0 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 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, 20 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
12:35on time on time
12:39≈ on time ≈ on time
12:44≈ on time ≈ on time
12:51≈ on time ≈ +1 min
12:58≈ on time ≈ +1 min
13: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 13:12Partial coverage0 min—
Sat 7 NovVught 13:120 min—
Fri 6 NovVught 13:13No data—
Thu 5 NovVught 13:12No data—
Wed 4 NovVught 13:13+1 min—
Tue 3 NovVught 13:12No data—
Mon 2 NovVught 13:12No data—
Sun 1 NovVught 13:140 min—
Sat 31 OctVught 13:180 min—
Fri 30 OctVught 13:15Partial coverage0 min—
Thu 29 Oct's-Hertogenbosch 13:320 min—
Wed 28 Oct's-Hertogenbosch 13:410 min—
Tue 27 Oct's-Hertogenbosch 13:29No data—
Mon 26 Oct's-Hertogenbosch 13:29No data—
Sun 25 OctVught 13:12No data—
Sat 24 OctVught 13:120 min—
Fri 23 OctVught 13:13No data—
Thu 22 OctVught 13:150 min—
Wed 21 OctVught 13:12No data—
Tue 20 OctVught 13:130 min—
Mon 19 OctVught 13:130 min—
Sun 18 OctVught 13:12Partial coverage+2 min+2 min
Sat 17 OctVught 13:14No data—
Fri 16 OctVught 13:12No data—
Thu 15 OctVught 13:23No data—
Wed 14 OctVught 13:25No data—
Tue 13 OctVught 13:13No data—
Mon 12 OctVught 13:13No data—
Sun 11 OctVught 13:13Partial coverage0 min—
Sat 10 OctVught 13:130 min—