Train NS 6527 's-Hertogenbosch – Deurne

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 08:58 from 's-Hertogenbosch · Fri 20 Nov

Next departure 08:58 today · 's-Hertogenbosch
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 14 full · 9 partial · 6 no data
On-time · 90 days
94%
34/36 runs under 3 min
RT coverage: 20 full · 16 partial · 51 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: +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

  • Wed 11 Nov Max en route +5 min · last fix heading to Helmond Brouwhuis +4 min
  • Sat 14 Nov Max en route +4 min · last fix heading to Helmond Brouwhuis +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 34
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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