Train NS 6555 's-Hertogenbosch → Deurne

's-Hertogenbosch 15:58 → Deurne 16:57 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 15:58 from 's-Hertogenbosch · Sat 21 Nov

Next departure 15:58 today · 's-Hertogenbosch
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 18 full · 4 partial · 7 no data
On-time · 90 days
91%
31/34 runs under 3 min
RT coverage: 27 full · 7 partial · 53 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: +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

  • Fri 13 Nov Max en route +12 min · last fix heading to Helmond Brouwhuis +12 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Helmond Brouwhuis +5 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Helmond Brouwhuis +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 31
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 83% W n=6
  • 100% T n=3
  • 80% F n=5
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 34 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:58on time on time
16:02≈ on time ≈ on time
16:09≈ on time ≈ on time
16:15≈ on time ≈ on time
16:21≈ on time ≈ on time
16:25 / 16:36≈ on time ≈ +1 min
16:42≈ on time ≈ +1 min
16:45≈ on time ≈ +1 min
16:49≈ on time ≈ +1 min
16:52≈ on time ≈ +1 min
16:57on 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
Fri 20 NovHelmond Brouwhuis 17:08Partial coverage+1 min+2 min
Thu 19 NovHelmond Brouwhuis 17:09+1 min+1 min
Wed 18 NovHelmond Brouwhuis 17:09+4 min+4 min
Tue 17 NovHelmond Brouwhuis 17:090 min—
Mon 16 NovHelmond Brouwhuis 17:09+1 min+1 min
Sun 15 NovEindhoven Strijp-S 16:340 min—
Sat 14 NovHelmond Brouwhuis 17:07Partial coverage0 min—
Fri 13 NovHelmond Brouwhuis 17:19Partial coverage+12 min+12 min
Thu 12 NovHelmond Brouwhuis 17:080 min—
Wed 11 NovHelmond Brouwhuis 17:070 min—
Tue 10 NovHelmond Brouwhuis 17:08+1 min+1 min
Mon 9 NovHelmond Brouwhuis 17:070 min—
Sun 8 NovEindhoven Strijp-S 16:390 min—
Sat 7 NovHelmond Brouwhuis 17:080 min—
Fri 6 NovHelmond Brouwhuis 17:08Partial coverage0 min—
Thu 5 NovHelmond Brouwhuis 17:07No data—
Wed 4 NovHelmond Brouwhuis 17:070 min—
Tue 3 NovHelmond Brouwhuis 17:070 min—
Mon 2 NovHelmond Brouwhuis 17:07No data—
Sun 1 NovEindhoven Strijp-S 16:360 min—
Sat 31 OctEindhoven Strijp-S 16:360 min—
Fri 30 OctEindhoven Strijp-S 16:37No data—
Thu 29 OctHelmond Brouwhuis 17:07No data—
Wed 28 OctHelmond Brouwhuis 17:070 min—
Tue 27 OctHelmond Brouwhuis 17:070 min—
Mon 26 OctHelmond Brouwhuis 17:07No data—
Sun 25 OctEindhoven Strijp-S 16:37No data—
Sat 24 OctHelmond Brouwhuis 17:080 min—
Fri 23 OctHelmond Brouwhuis 17:10No data—
Thu 22 OctHelmond Brouwhuis 17:08No data—