Train NS 6551 's-Hertogenbosch – Deurne

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:58 from 's-Hertogenbosch · Sun 8 Nov

Next departure 14:58 today · 's-Hertogenbosch
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 13 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Tue 6 Oct Max en route +32 min · last fix heading to Eindhoven Centraal +32 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
14:58on time on time
15:03≈ on time ≈ on time
15:09≈ on time ≈ on time
15:16≈ on time ≈ on time
15:22≈ on time ≈ on time
15:25 / 15:36≈ on time ≈ on time
15:44≈ on time ≈ +1 min
15:47≈ on time ≈ +1 min
15:50≈ on time ≈ +1 min
15:53≈ on time ≈ +1 min
15:58on time +1 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
Sat 7 NovHelmond Brouwhuis 16:09Partial coverage0 min—
Fri 6 NovHelmond Brouwhuis 16:08No data—
Thu 5 NovHelmond Brouwhuis 16:09No data—
Wed 4 NovHelmond Brouwhuis 16:090 min—
Tue 3 NovHelmond Brouwhuis 16:090 min—
Mon 2 NovHelmond Brouwhuis 16:09No data—
Sun 1 NovEindhoven Strijp-S 15:370 min—
Sat 31 OctEindhoven Strijp-S 15:36+1 min+2 min
Fri 30 OctEindhoven Strijp-S 15:370 min—
Thu 29 OctHelmond Brouwhuis 16:08No data—
Wed 28 OctHelmond Brouwhuis 16:170 min—
Tue 27 OctHelmond Brouwhuis 16:09No data—
Mon 26 OctHelmond Brouwhuis 16:100 min—
Sun 25 OctEindhoven Strijp-S 15:36No data—
Sat 24 OctHelmond Brouwhuis 16:10+1 min+1 min
Fri 23 OctHelmond Brouwhuis 16:10No data—
Thu 22 OctHelmond Brouwhuis 16:08No data—
Wed 21 OctHelmond Brouwhuis 16:08No data—
Tue 20 OctHelmond Brouwhuis 16:080 min—
Mon 19 OctHelmond Brouwhuis 16:080 min—
Sun 18 OctEindhoven Strijp-S 15:360 min—
Sat 17 OctHelmond Brouwhuis 16:090 min—
Fri 16 OctHelmond Brouwhuis 16:10No data—
Thu 15 OctHelmond Brouwhuis 16:10No data—
Wed 14 OctHelmond Brouwhuis 16:08No data—
Tue 13 OctHelmond Brouwhuis 16:08No data—
Mon 12 OctHelmond Brouwhuis 16:080 min—
Sun 11 OctEindhoven Strijp-S 15:36+1 min—
Sat 10 OctHelmond Brouwhuis 16:08+1 min+2 min
Fri 9 OctHelmond Brouwhuis 16:070 min—