Train NS 6584 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 22:37 from Deurne · Fri 20 Nov

Next departure 22:37 today · Deurne
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 21 full · 3 partial · 4 no data
On-time · 90 days
86%
32/37 runs under 3 min
RT coverage: 32 full · 5 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sun 11 Oct Max en route +11 min · last fix heading to Vught +10 min
  • Sat 10 Oct Max en route +5 min · last fix heading to — +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 13 Nov Max en route +4 min · last fix heading to — +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 32
  • 3–10 min 11% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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
22:37on time on time
22:42≈ on time ≈ on time
22:46≈ on time ≈ +1 min
22:49≈ on time ≈ +1 min
22:51≈ on time ≈ +1 min
22:59 / 23:05≈ on time ≈ +2 min
23:09≈ on time ≈ +2 min
23:14≈ on time ≈ +3 min
23:21≈ on time ≈ +3 min
23:28≈ on time ≈ +4 min
23:33on time +4 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 19 Nov— 23:340 min—
Wed 18 Nov— 23:34+1 min—
Tue 17 Nov— 23:54+2 min+2 min
Mon 16 NovBoxtel 23:39Partial coverage+2 min+3 min
Sun 15 NovVught 23:42Partial coverage0 min—
Sat 14 NovHelmond Brandevoort 23:34Partial coverage0 min—
Fri 13 Nov— 23:42+4 min+4 min
Thu 12 Nov— 23:340 min—
Wed 11 Nov— 23:340 min—
Tue 10 Nov— 23:43+4 min+4 min
Mon 9 Nov— 23:34+1 min+1 min
Sun 8 NovVught 23:43+1 min—
Sat 7 NovBoxtel 23:34+1 min+1 min
Fri 6 Nov— 23:39+2 min+2 min
Thu 5 Nov— 23:34No data—
Wed 4 Nov— 23:43+4 min+4 min
Tue 3 Nov— 23:34No data—
Mon 2 Nov— 23:34+3 min+3 min
Sun 1 NovVught 23:430 min—
Sat 31 OctBoxtel 23:400 min—
Fri 30 Oct— 23:320 min—
Thu 29 Oct— 23:34+2 min+2 min
Wed 28 Oct— 23:520 min—
Tue 27 Oct— 00:130 min—
Mon 26 Oct— 23:340 min—
Sun 25 OctVught 23:43No data—
Sat 24 OctDeurne 23:34No data—
Thu 22 Oct— 23:370 min—
Wed 21 Oct— 22:55No data—
Tue 20 Oct— 23:390 min—