Train NS 6564 Deurne – 's-Hertogenbosch

Deurne 17:37 → 's-Hertogenbosch 18:33 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November No data

Next service: today 17:37 from Deurne · Wed 18 Nov

Next departure 17:37 today · Deurne
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 5 full · 15 partial · 9 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 5 full · 25 partial · 56 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: +3 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 +6 min · last fix heading to Vught +6 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Best +4 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Vught +4 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Helmond Brandevoort +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 26
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
17:37on time on time
17:42≈ on time ≈ on time
17:46≈ on time ≈ on time
17:49≈ on time ≈ on time
17:51≈ on time ≈ +1 min
17:59 / 18:05≈ on time ≈ +1 min
18:09≈ on time ≈ +1 min
18:14≈ on time ≈ +1 min
18:21≈ on time ≈ +2 min
18:28≈ on time ≈ +2 min
18:33on time +2 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 NovDeurne 18:34No data—
Mon 16 NovBoxtel 18:39Partial coverage+3 min+3 min
Sun 15 NovVught 18:44Partial coverage+4 min+4 min
Sat 14 NovVught 18:43Partial coverage0 min—
Fri 13 NovVught 18:42Partial coverage0 min—
Thu 12 NovBoxtel 18:34Partial coverage0 min—
Wed 11 NovBest 18:42Partial coverage+4 min+4 min
Tue 10 NovBoxtel 18:34Partial coverage0 min—
Mon 9 NovEindhoven Strijp-S 18:34Partial coverage0 min—
Sun 8 NovVught 18:42Partial coverage0 min—
Sat 7 NovVught 18:42Partial coverage0 min—
Fri 6 NovVught 18:42Partial coverage0 min—
Thu 5 NovEindhoven Strijp-S 18:34No data—
Wed 4 NovBest 18:34Partial coverage0 min—
Tue 3 NovEindhoven Strijp-S 18:34No data—
Mon 2 NovEindhoven Strijp-S 18:23No data—
Sun 1 NovVught 18:44+2 min+2 min
Sat 31 OctVught 18:45+2 min+3 min
Fri 30 OctVught 18:42No data—
Thu 29 OctHelmond Brandevoort 18:35Partial coverage0 min—
Wed 28 OctEindhoven Strijp-S 18:34No data—
Tue 27 OctEindhoven Centraal 18:35Partial coverage0 min—
Mon 26 OctEindhoven Strijp-S 18:42Partial coverage0 min—
Sun 25 OctVught 18:45No data—
Sat 24 OctVught 18:420 min—
Fri 23 OctVught 19:050 min—
Thu 22 OctVught 18:42No data—
Wed 21 OctVught 18:42No data—
Tue 20 OctVught 18:420 min—
Mon 19 OctVught 18:42No data—