Train NS 6531 's-Hertogenbosch – Deurne

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

✓ Today’s run finished

Today, last fix heading to Helmond Brouwhuis at 11:09 No data

  1. 's-Hertogenbosch09:58
  2. Boxtel10:09
  3. Best10:15
  4. Eindhoven Centraal10:25
  5. Helmond 't Hout10:46
  6. Helmond Brouwhuis10:53
  7. Deurne10:58

Next service: tomorrow 09:58 from 's-Hertogenbosch · Fri 6 Nov

Next departure 09:58 tomorrow · 's-Hertogenbosch
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 69 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

  • Thu 8 Oct Max en route +9 min · last fix heading to Helmond Brouwhuis +9 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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