Train NS 6553 's-Hertogenbosch – Deurne

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

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

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

Next departure 15:28 today · 's-Hertogenbosch
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 9 full · 11 partial · 9 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 14 full · 16 partial · 56 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

  • Wed 11 Nov Max en route +6 min · last fix heading to Helmond Brouwhuis +6 min
  • Sun 11 Oct Max en route +9 min · last fix heading to Helmond Brouwhuis +5 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Helmond Brouwhuis +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 27
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=4
  • 80% W n=5
  • 100% T n=3
  • 100% F n=2
  • 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, 30 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
15:28on time on time
15:33≈ on time ≈ on time
15:39≈ on time ≈ on time
15:45≈ on time ≈ +1 min
15:51≈ on time ≈ +1 min
15:55 / 16:07≈ on time ≈ +1 min
16:13≈ on time ≈ +2 min
16:16≈ on time ≈ +2 min
16:20≈ on time ≈ +2 min
16:23≈ on time ≈ +2 min
16:28on 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 NovHelmond Brouwhuis 16:39Partial coverage+1 min+1 min
Tue 17 NovHelmond Brouwhuis 16:59Partial coverage0 min—
Mon 16 NovHelmond Brouwhuis 16:39Partial coverage0 min—
Sun 15 NovHelmond Brouwhuis 16:38+2 min+2 min
Sat 14 NovHelmond Brouwhuis 16:370 min—
Fri 13 NovHelmond Brouwhuis 16:39+2 min+2 min
Thu 12 NovHelmond Brouwhuis 16:39Partial coverage+3 min+3 min
Wed 11 NovHelmond Brouwhuis 16:44Partial coverage+6 min+6 min
Tue 10 NovHelmond Brouwhuis 16:38Partial coverage0 min—
Mon 9 NovHelmond Brouwhuis 16:39Partial coverage+3 min+4 min
Sun 8 NovHelmond Brouwhuis 16:390 min—
Sat 7 NovHelmond Brouwhuis 16:39+2 min+2 min
Fri 6 NovHelmond Brouwhuis 16:39No data—
Thu 5 NovHelmond Brouwhuis 16:39No data—
Wed 4 NovHelmond Brouwhuis 16:39Partial coverage0 min—
Tue 3 NovHelmond Brouwhuis 16:38Partial coverage0 min—
Mon 2 NovHelmond Brouwhuis 16:38Partial coverage0 min—
Sun 1 NovEindhoven Strijp-S 16:060 min—
Sat 31 OctEindhoven Strijp-S 16:050 min—
Fri 30 OctEindhoven Strijp-S 16:07No data—
Thu 29 OctHelmond Brouwhuis 16:390 min—
Wed 28 OctHelmond Brouwhuis 16:380 min—
Tue 27 OctHelmond Brouwhuis 16:38No data—
Mon 26 OctHelmond Brouwhuis 16:41No data—
Sun 25 OctHelmond Brouwhuis 16:37No data—
Sat 24 OctHelmond Brouwhuis 16:38Partial coverage0 min—
Fri 23 OctHelmond Brouwhuis 16:41No data—
Thu 22 OctHelmond Brouwhuis 16:38No data—
Wed 21 OctHelmond Brouwhuis 16:39No data—
Tue 20 OctHelmond Brouwhuis 16:38No data—