Train NS 6563 's-Hertogenbosch – Deurne

's-Hertogenbosch 17:58 → Deurne 18:58 Daily 1 h 00 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 17:58 from 's-Hertogenbosch · Tue 17 Nov

Next departure 17:58 today · 's-Hertogenbosch
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 12 full · 10 partial · 7 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 17 full · 14 partial · 55 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 Deurne, 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 23 Oct Max en route +5 min · last fix heading to Helmond Brouwhuis +5 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Eindhoven Strijp-S +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Eindhoven Centraal +4 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 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 60% 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, 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
17:58on time on time
18:03≈ on time ≈ on time
18:09≈ on time ≈ +1 min
18:15≈ on time ≈ +1 min
18:21≈ on time ≈ +1 min
18:25 / 18:37≈ on time ≈ +2 min
18:43≈ on time ≈ +3 min
18:46≈ on time ≈ +3 min
18:50≈ on time ≈ +3 min
18:53≈ on time ≈ +3 min
18:58on time +3 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
Mon 16 NovEindhoven Strijp-S 19:00Partial coverage0 min—
Sun 15 NovEindhoven Strijp-S 18:37+1 min+2 min
Sat 14 NovHelmond Brouwhuis 19:080 min—
Fri 13 NovHelmond Brouwhuis 19:04+3 min+3 min
Thu 12 NovEindhoven Strijp-S 18:59Partial coverage0 min—
Wed 11 NovBoxtel 18:59Partial coverage+1 min+1 min
Tue 10 NovEindhoven Strijp-S 18:59Partial coverage+1 min+1 min
Mon 9 NovBoxtel 18:59Partial coverage0 min—
Sun 8 NovEindhoven Strijp-S 18:380 min—
Sat 7 NovHelmond Brouwhuis 19:090 min—
Fri 6 NovHelmond 't Hout 18:590 min+1 min
Thu 5 NovBoxtel 18:59No data—
Wed 4 NovBest 18:59Partial coverage0 min—
Tue 3 NovBoxtel 18:59No data—
Mon 2 NovBoxtel 18:59Partial coverage+3 min+3 min
Sun 1 NovEindhoven Strijp-S 18:39+5 min+5 min
Sat 31 OctEindhoven Strijp-S 18:360 min—
Fri 30 OctEindhoven Strijp-S 18:360 min—
Thu 29 OctOss 18:590 min—
Wed 28 OctBoxtel 19:000 min—
Tue 27 OctOss 19:05No data—
Mon 26 OctBoxtel 18:590 min—
Sun 25 OctEindhoven Strijp-S 18:36No data—
Sat 24 OctHelmond Brouwhuis 19:09Partial coverage0 min—
Fri 23 OctHelmond Brouwhuis 19:07Partial coverage+5 min+5 min
Thu 22 OctHelmond Brandevoort 19:00No data—
Wed 21 OctEindhoven Centraal 19:00No data—
Tue 20 OctHelmond 't Hout 19:00No data—
Mon 19 OctHelmond Brandevoort 18:59Partial coverage0 min—
Sun 18 OctEindhoven Strijp-S 18:360 min—