Train NS 6536 Deurne – 's-Hertogenbosch

Deurne 10:37 → 's-Hertogenbosch 11:33 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 10:37 from Deurne · Thu 19 Nov

Next departure 10:37 today · Deurne
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 9 full · 11 partial · 9 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 14 full · 17 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at 's-Hertogenbosch, 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 9 Oct Max en route +5 min · last fix heading to Vught +5 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Vught +4 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Vught +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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:37on time on time
10:42≈ on time ≈ on time
10:46≈ on time ≈ +1 min
10:49≈ on time ≈ +1 min
10:51≈ on time ≈ +1 min
10:59 / 11:05≈ on time ≈ +1 min
11:09≈ on time ≈ +2 min
11:14≈ on time ≈ +2 min
11:21≈ on time ≈ +2 min
11:28≈ on time ≈ +3 min
11:33on 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
Wed 18 NovVught 11:43Partial coverage+1 min—
Tue 17 NovVught 11:44Partial coverage+4 min+4 min
Mon 16 NovVught 11:44Partial coverage+2 min+2 min
Sun 15 NovVught 11:45+4 min+4 min
Sat 14 NovVught 11:420 min—
Fri 13 NovVught 11:420 min—
Thu 12 NovVught 11:43Partial coverage0 min—
Wed 11 NovVught 11:44Partial coverage+3 min+3 min
Tue 10 NovVught 11:42Partial coverage0 min—
Mon 9 NovVught 11:43Partial coverage+1 min+1 min
Sun 8 NovVught 11:43+1 min+1 min
Sat 7 NovVught 11:430 min—
Fri 6 NovVught 11:42No data—
Thu 5 NovVught 11:42No data—
Wed 4 NovVught 11:42Partial coverage+1 min—
Tue 3 NovVught 11:44No data—
Mon 2 NovVught 11:42No data—
Sun 1 NovVught 11:440 min+1 min
Sat 31 OctVught 11:430 min—
Fri 30 OctVught 11:420 min—
Thu 29 Oct's-Hertogenbosch 11:54No data—
Wed 28 Oct's-Hertogenbosch 11:550 min—
Tue 27 Oct's-Hertogenbosch 11:55No data—
Mon 26 Oct's-Hertogenbosch 11:54No data—
Sun 25 OctVught 11:43No data—
Sat 24 OctVught 11:43Partial coverage+1 min—
Fri 23 OctVught 11:44Partial coverage0 min—
Thu 22 OctVught 11:42Partial coverage0 min—
Wed 21 OctVught 11:42No data—
Tue 20 OctVught 11:42Partial coverage0 min—