Train NS 6580 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 21:37 from Deurne · Sat 7 Nov

Next departure 21:37 today · Deurne
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 11 full · 3 partial · 13 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 15 full · 3 partial · 27 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

  • Wed 4 Nov Max en route +4 min · last fix heading to — +3 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Eindhoven Centraal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 75% W n=4
  • 100% T n=1
  • 100% F n=4
  • 0% S n=1
  • 100% S n=3

Stops and timetable

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

Last 90 days, 18 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
21:37on time on time
21:42≈ on time ≈ on time
21:46≈ on time ≈ on time
21:49≈ on time ≈ +1 min
21:51≈ on time ≈ +1 min
21:59 / 22:05≈ on time ≈ +1 min
22:09≈ on time ≈ +2 min
22:14≈ on time ≈ +2 min
22:21≈ on time ≈ +2 min
22:28≈ on time ≈ +2 min
22: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
Fri 6 Nov— 22:37+1 min+3 min
Thu 5 Nov— 22:34No data—
Wed 4 Nov— 22:39+3 min+4 min
Tue 3 Nov— 22:350 min—
Sun 1 NovVught 22:430 min—
Sat 31 OctVught 22:43No data—
Fri 30 Oct— 22:36No data—
Wed 28 Oct— 22:340 min—
Tue 27 Oct— 22:35No data—
Mon 26 Oct— 22:340 min—
Sun 25 OctVught 22:42No data—
Sat 24 OctVught 22:42No data—
Fri 23 Oct— 22:38+2 min+2 min
Thu 22 Oct— 22:41No data—
Wed 21 Oct— 22:36No data—
Tue 20 Oct— 22:34No data—
Mon 19 Oct— 22:34No data—
Sun 18 OctVught 22:42Partial coverage0 min—
Sat 17 OctVught 22:42No data—
Fri 16 Oct— 22:35+1 min+1 min
Thu 15 Oct— 22:55No data—
Wed 14 Oct— 22:340 min—
Tue 13 Oct— 22:35No data—
Mon 12 Oct— 22:39+2 min+2 min
Sun 11 OctVught 22:42Partial coverage0 min—
Sat 10 OctEindhoven Centraal 22:39Partial coverage+3 min+3 min
Fri 9 Oct— 22:340 min—
Thu 8 Oct— 22:37+1 min—
Wed 7 Oct— 22:340 min—
Tue 6 Oct— 21:550 min—