Train NS 6535 's-Hertogenbosch – Deurne

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 10:58 from 's-Hertogenbosch · Fri 6 Nov

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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