Train NS 6573 's-Hertogenbosch – Deurne

's-Hertogenbosch 20:28 → Deurne 21:27 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 20:28 from 's-Hertogenbosch · Thu 19 Nov

Next departure 20:28 today · 's-Hertogenbosch
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 18 full · 2 partial · 8 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 26 full · 5 partial · 25 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: +2 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 13 Nov Max en route +7 min · last fix heading to — +7 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 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=3
  • 80% F n=5
  • 100% S n=4
  • 100% 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
20:28on time on time
20:32≈ on time ≈ on time
20:39≈ on time ≈ on time
20:45≈ on time ≈ on time
20:51≈ on time ≈ +1 min
20:55 / 21:06≈ on time ≈ +1 min
21:12≈ on time ≈ +1 min
21:15≈ on time ≈ +1 min
21:19≈ on time ≈ +1 min
21:22≈ on time ≈ +1 min
21:27on 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
Wed 18 Nov— 21:29+2 min+2 min
Tue 17 Nov— 21:280 min—
Mon 16 Nov— 21:290 min—
Sun 15 NovHelmond Brouwhuis 21:38Partial coverage0 min—
Sat 14 NovHelmond Brouwhuis 21:38Partial coverage+1 min+2 min
Fri 13 Nov— 21:34+7 min+7 min
Thu 12 Nov— 21:290 min—
Wed 11 Nov— 21:280 min—
Tue 10 Nov— 21:29+1 min+2 min
Mon 9 Nov— 21:280 min—
Sun 8 NovHelmond Brouwhuis 21:380 min—
Sat 7 NovHelmond Brouwhuis 21:38+1 min+2 min
Fri 6 Nov— 21:29+1 min+2 min
Thu 5 Nov— 21:29No data—
Wed 4 Nov— 21:29+1 min+1 min
Mon 2 Nov— 21:280 min—
Sun 1 NovEindhoven Strijp-S 21:040 min—
Sat 31 OctEindhoven Strijp-S 21:060 min—
Fri 30 Oct— 20:57No data—
Thu 29 Oct— 21:00+2 min+4 min
Wed 28 Oct— 21:290 min—
Tue 27 Oct— 21:31No data—
Mon 26 Oct— 21:33No data—
Sun 25 OctHelmond Brouwhuis 21:38No data—
Sat 24 OctHelmond Brouwhuis 21:37No data—
Fri 23 Oct— 21:29+1 min+1 min
Thu 22 Oct— 21:35No data—
Wed 21 Oct— 21:31No data—
Tue 20 Oct— 21:28No data—
Mon 19 Oct— 21:28No data—