Train NS 6532 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

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

Next departure 09:37 today · Deurne
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 10 full · 10 partial · 9 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 16 full · 14 partial · 56 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 '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

  • Mon 9 Nov Max en route +10 min · last fix heading to Vught +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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