Train NS 6565 's-Hertogenbosch – Deurne

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 18:28 from 's-Hertogenbosch · Fri 6 Nov

Next departure 18:28 today · 's-Hertogenbosch
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 11 full · 3 partial · 15 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 14 full · 3 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 9 Oct Max en route +7 min · last fix heading to Vught +7 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Helmond Brouwhuis +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=2
  • 100% T n=2
  • 33% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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:28on time on time
18:33≈ on time ≈ on time
18:39≈ on time ≈ on time
18:45≈ on time ≈ on time
18:51≈ on time ≈ on time
18:55 / 19:07≈ on time ≈ on time
19:13≈ on time ≈ on time
19:16≈ on time ≈ on time
19:20≈ on time ≈ on time
19:23≈ on time ≈ on time
19:28on time on time

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 5 Nov— 19:33No data—
Wed 4 Nov— 19:32No data—
Tue 3 Nov— 19:29No data—
Mon 2 NovVught 19:33Partial coverage0 min—
Sun 1 NovEindhoven Strijp-S 19:040 min—
Sat 31 OctEindhoven Strijp-S 19:06+1 min—
Fri 30 OctEindhoven Strijp-S 19:06No data—
Thu 29 Oct— 19:290 min—
Wed 28 OctOss 19:290 min—
Tue 27 OctOss 19:35No data—
Mon 26 OctOss 19:300 min—
Sun 25 OctHelmond Brouwhuis 19:37No data—
Sat 24 OctHelmond Brouwhuis 19:45No data—
Fri 23 OctHelmond Brouwhuis 19:37Partial coverage+4 min+4 min
Thu 22 OctBest 19:35No data—
Wed 21 OctBoxtel 19:30No data—
Tue 20 OctBest 19:30No data—
Mon 19 OctBoxtel 19:30No data—
Sun 18 OctHelmond Brouwhuis 19:370 min—
Sat 17 OctHelmond Brouwhuis 19:38No data—
Fri 16 OctHelmond Brouwhuis 19:360 min—
Thu 15 Oct's-Hertogenbosch 19:37No data—
Wed 14 OctHelmond Brouwhuis 19:37No data—
Tue 13 OctBoxtel 19:30No data—
Mon 12 OctBest 19:30Partial coverage0 min—
Sun 11 OctHelmond Brouwhuis 19:370 min—
Sat 10 OctHelmond Brouwhuis 19:390 min—
Fri 9 OctVught 19:34+7 min+7 min
Thu 8 Oct— 19:290 min—
Wed 7 Oct— 19:290 min—