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: Sunday 8 November 0 min

Next service: today 09:37 from Deurne · Mon 9 Nov

Next departure 09:37 today · Deurne
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 10 full · 5 partial · 14 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 13 full · 7 partial · 66 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=3
  • 100% W n=2
  • 100% T n=3
  • 100% F n=1
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 20 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 ≈ on time
09:59 / 10:05≈ on time ≈ on time
10:09≈ on time ≈ on time
10:14≈ on time ≈ on time
10:21≈ on time ≈ on time
10:28≈ on time ≈ on time
10:33on time on time

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
Sun 8 NovVught 10:42Partial coverage0 min—
Sat 7 NovVught 10:44Partial coverage+3 min+3 min
Fri 6 NovVught 10:43No data—
Thu 5 NovVught 10:43No data—
Wed 4 NovVught 10:420 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:420 min—
Fri 23 OctVught 10:42No data—
Thu 22 OctVught 10:440 min—
Wed 21 OctVught 10:45No data—
Tue 20 OctVught 10:430 min—
Mon 19 OctVught 10:430 min—
Sun 18 OctVught 10:43Partial coverage0 min—
Sat 17 OctVught 10:42Partial coverage0 min—
Fri 16 OctVught 10:42No data—
Thu 15 OctVught 10:43No data—
Wed 14 OctVught 10:42No data—
Tue 13 OctVught 10:46No data—
Mon 12 OctVught 10:42No data—
Sun 11 OctVught 10:42Partial coverage0 min—
Sat 10 OctVught 10:43Partial coverage0 min—