Train NS 6530 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

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

Next departure 09:07 today · Deurne
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 11 full · 12 partial · 6 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 17 full · 16 partial · 54 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: +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

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

Distribution · 90 days

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

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

On-time by weekday

  • 67% M n=3
  • 80% T n=5
  • 100% W n=6
  • 100% T n=4
  • 100% F n=4
  • 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, 33 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:07on time on time
09:12≈ on time ≈ on time
09:16≈ on time ≈ on time
09:19≈ on time ≈ +1 min
09:21≈ on time ≈ +1 min
09:29 / 09:35≈ on time ≈ +1 min
09:39≈ on time ≈ +1 min
09:44≈ on time ≈ +1 min
09:51≈ on time ≈ +1 min
09:58≈ on time ≈ +2 min
10:03on 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:14Partial coverage+2 min+2 min
Tue 17 NovVught 10:13Partial coverage0 min—
Mon 16 NovVught 10:17Partial coverage+4 min+4 min
Sun 15 NovVught 10:120 min—
Sat 14 NovVught 10:14+3 min+3 min
Fri 13 NovVught 10:120 min—
Thu 12 NovVught 10:13Partial coverage+1 min+1 min
Wed 11 NovVught 10:14Partial coverage+2 min+2 min
Tue 10 NovVught 10:23Partial coverage+9 min+9 min
Mon 9 NovVught 10:14Partial coverage+2 min+2 min
Sun 8 NovVught 10:120 min—
Sat 7 NovVught 10:13+3 min+3 min
Fri 6 NovVught 10:13No data—
Thu 5 NovVught 10:13No data—
Wed 4 NovVught 10:13Partial coverage0 min—
Tue 3 NovVught 10:14Partial coverage0 min—
Mon 2 NovVught 10:12No data—
Sun 1 NovVught 10:15+1 min+1 min
Sat 31 OctVught 10:14+1 min+2 min
Fri 30 OctVught 10:120 min—
Thu 29 Oct's-Hertogenbosch 10:290 min—
Wed 28 Oct's-Hertogenbosch 10:320 min—
Tue 27 Oct's-Hertogenbosch 10:290 min—
Mon 26 Oct's-Hertogenbosch 10:29No data—
Sun 25 OctVught 10:13No data—
Sat 24 OctVught 10:13Partial coverage+1 min—
Fri 23 OctVught 10:15No data—
Thu 22 OctVught 10:19Partial coverage0 min—
Wed 21 OctVught 10:12Partial coverage0 min—
Tue 20 OctVught 10:13No data—