Train NS 6566 Deurne – 's-Hertogenbosch

Deurne 18:07 → 's-Hertogenbosch 19:03 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November +1 min

Next service: today 18:07 from Deurne · Fri 20 Nov

Next departure 18:07 today · Deurne
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 7 full · 15 partial · 7 no data
On-time · 90 days
87%
27/31 runs under 3 min
RT coverage: 12 full · 19 partial · 49 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: +4 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 +20 min · last fix heading to Helmond Brandevoort +20 min
  • Wed 11 Nov Max en route +9 min · last fix heading to Helmond Brouwhuis +9 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Vught +4 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Vught +3 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 87% · 27
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 67% W n=3
  • 100% T n=5
  • 100% F n=5
  • 75% S n=4
  • 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
18:07on time on time
18:12≈ on time ≈ on time
18:16≈ on time ≈ +1 min
18:19≈ on time ≈ +1 min
18:21≈ on time ≈ +1 min
18:29 / 18:35≈ on time ≈ +1 min
18:39≈ on time ≈ +2 min
18:44≈ on time ≈ +2 min
18:51≈ on time ≈ +3 min
18:58≈ on time ≈ +3 min
19:03on 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
Thu 19 NovHelmond Brandevoort 19:04Partial coverage+1 min—
Wed 18 NovBest 19:09Partial coverage+2 min+2 min
Tue 17 NovHelmond Brandevoort 19:24Partial coverage+20 min+20 min
Mon 16 NovHelmond Brandevoort 19:05Partial coverage0 min—
Sun 15 NovVught 19:14+4 min+4 min
Sat 14 NovVught 19:12Partial coverage0 min—
Fri 13 NovBoxtel 19:04Partial coverage+1 min+1 min
Thu 12 NovHelmond Brandevoort 19:04Partial coverage+1 min+1 min
Wed 11 NovHelmond Brouwhuis 19:22Partial coverage+9 min+9 min
Tue 10 NovHelmond Brandevoort 19:04Partial coverage+1 min+1 min
Mon 9 NovHelmond Brouwhuis 19:04Partial coverage0 min—
Sun 8 NovVught 19:13+1 min+1 min
Sat 7 NovVught 19:12Partial coverage0 min—
Fri 6 NovBest 18:59Partial coverage0 min—
Thu 5 NovHelmond Brouwhuis 19:04No data—
Wed 4 NovHelmond Brouwhuis 19:09No data—
Tue 3 NovHelmond Brouwhuis 19:05No data—
Mon 2 NovDeurne 19:04Partial coverage0 min—
Sun 1 NovVught 19:130 min—
Sat 31 OctVught 19:130 min—
Fri 30 OctBoxtel 19:080 min—
Thu 29 Oct— 19:04+3 min+3 min
Wed 28 OctHelmond Brouwhuis 19:11Partial coverage0 min—
Tue 27 Oct— 19:07No data—
Mon 26 OctDeurne 19:05No data—
Sun 25 OctVught 19:13No data—
Sat 24 OctVught 19:13No data—
Fri 23 OctVught 19:12+2 min+2 min
Thu 22 OctBest 19:13Partial coverage0 min—
Wed 21 OctEindhoven Strijp-S 19:05No data—