Train NS 6560 Deurne – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Vught at 17:42 +4 min

  1. Deurne16:37
  2. Helmond16:46
  3. Helmond 't Hout16:49
  4. Eindhoven Centraal16:59
  5. Best17:14
  6. Vught17:28
  7. 's-Hertogenbosch17:33

Next service: tomorrow 16:37 from Deurne · Fri 20 Nov

Next departure 16:37 tomorrow · Deurne
On-time · 30 days
70%
14/20 runs under 3 min
RT coverage: 11 full · 9 partial · 10 no data
On-time · 90 days
74%
23/31 runs under 3 min
RT coverage: 18 full · 13 partial · 56 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Tue 17 Nov Max en route +9 min · last fix heading to Vught +9 min
  • Sun 8 Nov Max en route +7 min · last fix heading to Vught +7 min
  • Fri 13 Nov Max en route +6 min · last fix heading to Vught +6 min
  • Wed 7 Oct Max en route +6 min · last fix heading to Vught +6 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Vught +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 23
  • 3–10 min 26% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
16:37on time on time
16:42≈ on time ≈ on time
16:46≈ on time ≈ +1 min
16:49≈ on time ≈ +1 min
16:51≈ on time ≈ +1 min
16:59 / 17:05≈ on time ≈ +2 min
17:09≈ +1 min ≈ +3 min
17:14≈ +1 min ≈ +3 min
17:21≈ +1 min ≈ +4 min
17:28≈ +1 min ≈ +4 min
17:33+1 min +5 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
Thu 19 NovVught 17:42Partial coverage+4 min+4 min
Wed 18 NovVught 17:42Partial coverage+3 min+3 min
Tue 17 NovVught 17:49Partial coverage+9 min+9 min
Mon 16 NovVught 17:43Partial coverage0 min—
Sun 15 NovVught 17:43+4 min+4 min
Sat 14 NovVught 17:420 min—
Fri 13 NovVught 17:48+6 min+6 min
Thu 12 NovVught 17:44Partial coverage+2 min+4 min
Wed 11 NovVught 17:44Partial coverage+5 min+5 min
Tue 10 NovVught 17:42Partial coverage+1 min—
Mon 9 NovVught 17:42Partial coverage+2 min+3 min
Sun 8 NovVught 17:49+7 min+7 min
Sat 7 NovVught 17:43+1 min+1 min
Fri 6 NovVught 17:42+1 min+1 min
Thu 5 NovVught 17:42No data—
Wed 4 NovVught 17:42No data—
Tue 3 NovVught 17:42No data—
Mon 2 NovVught 17:39No data—
Sun 1 NovVught 17:430 min—
Sat 31 OctVught 17:45+2 min+2 min
Fri 30 OctVught 17:430 min—
Thu 29 Oct's-Hertogenbosch 17:58No data—
Wed 28 Oct's-Hertogenbosch 17:570 min—
Tue 27 Oct's-Hertogenbosch 17:58No data—
Mon 26 Oct's-Hertogenbosch 17:580 min—
Sun 25 OctVught 17:44No data—
Sat 24 OctVught 17:42Partial coverage0 min—
Fri 23 OctVught 17:42No data—
Thu 22 OctVught 17:42No data—
Wed 21 OctVught 17:42No data—