Train NS 6576 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 20:37 from Deurne · Wed 18 Nov

Next departure 20:37 today · Deurne
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 15 full · 4 partial · 8 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 21 full · 7 partial · 27 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: +5 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 11 Nov Max en route +12 min · last fix heading to — +12 min
  • Tue 10 Nov Max en route +7 min · last fix heading to — +7 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 33% W n=3
  • 100% T n=4
  • 75% F n=4
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

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