Train NS 6555 's-Hertogenbosch – Deurne

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

✓ Today’s run finished

Today, last fix heading to Helmond Brouwhuis at 17:07 0 min

  1. 's-Hertogenbosch15:58
  2. Boxtel16:09
  3. Best16:15
  4. Eindhoven Centraal16:25
  5. Helmond 't Hout16:46
  6. Helmond Brouwhuis16:53
  7. Deurne16:58

Next service: tomorrow 15:58 from 's-Hertogenbosch · Tue 10 Nov

Next departure 15:58 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 11 full · 6 partial · 13 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 14 full · 9 partial · 65 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

  • Sat 10 Oct Max en route +5 min · last fix heading to Helmond Brouwhuis +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:03≈ 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:37≈ on time ≈ +1 min
16:43≈ on time ≈ +1 min
16:46≈ on time ≈ +1 min
16:50≈ on time ≈ +1 min
16:53≈ on time ≈ +1 min
16: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
Mon 9 NovHelmond Brouwhuis 17:07Partial coverage0 min—
Sun 8 NovEindhoven Strijp-S 16:390 min—
Sat 7 NovHelmond Brouwhuis 17:080 min—
Fri 6 NovHelmond Brouwhuis 17:080 min—
Thu 5 NovHelmond Brouwhuis 17:07No data—
Wed 4 NovHelmond Brouwhuis 17:07Partial coverage0 min—
Tue 3 NovHelmond Brouwhuis 17:07Partial coverage0 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:08Partial coverage0 min—
Fri 23 OctHelmond Brouwhuis 17:10No data—
Thu 22 OctHelmond Brouwhuis 17:08No data—
Wed 21 OctHelmond Brouwhuis 17:080 min—
Tue 20 OctHelmond Brouwhuis 17:08No data—
Mon 19 OctHelmond Brouwhuis 17:08Partial coverage0 min—
Sun 18 OctEindhoven Strijp-S 16:38+1 min+2 min
Sat 17 OctHelmond Brouwhuis 17:07No data—
Fri 16 OctHelmond Brouwhuis 17:070 min—
Thu 15 OctHelmond Brouwhuis 17:09No data—
Wed 14 OctHelmond Brouwhuis 17:08No data—
Tue 13 OctHelmond Brouwhuis 17:10No data—
Mon 12 OctHelmond Brouwhuis 17:09Partial coverage0 min—
Sun 11 OctEindhoven Strijp-S 16:37+1 min+1 min