Train NS 6578 Deurne → 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 21:07 from Deurne · Sat 21 Nov

Next departure 21:07 today · Deurne
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 20 full · 2 partial · 5 no data
On-time · 90 days
87%
27/31 runs under 3 min
RT coverage: 28 full · 3 partial · 25 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: +2 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

  • Fri 9 Oct Max en route +11 min · last fix heading to — +11 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min
  • Wed 7 Oct Max en route +3 min · last fix heading to — +3 min
  • Mon 2 Nov Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 27
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=3
  • 100% T n=4
  • 80% W n=5
  • 100% T n=4
  • 86% F n=7
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 31 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:07on time on time
21:12≈ on time ≈ on time
21:16≈ on time ≈ +1 min
21:19≈ on time ≈ +1 min
21:21≈ on time ≈ +1 min
21:29 / 21:35≈ on time ≈ +1 min
21:39≈ on time ≈ +2 min
21:44≈ on time ≈ +2 min
21:51≈ on time ≈ +3 min
21:58≈ on time ≈ +3 min
22:03on time +3 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 20 Nov— 22:040 min—
Thu 19 Nov— 22:040 min—
Wed 18 Nov— 22:09+2 min+2 min
Tue 17 Nov— 22:040 min—
Sun 15 NovVught 22:130 min—
Sat 14 NovVught 22:12Partial coverage0 min—
Fri 13 Nov— 22:040 min—
Thu 12 Nov— 22:07+1 min+1 min
Wed 11 Nov— 22:040 min—
Tue 10 Nov— 22:09+2 min+2 min
Mon 9 Nov— 22:040 min—
Sun 8 NovVught 22:120 min—
Sat 7 NovVught 22:13Partial coverage0 min—
Fri 6 Nov— 22:040 min—
Thu 5 Nov— 22:07No data—
Wed 4 Nov— 22:07+2 min+2 min
Mon 2 Nov— 22:09+3 min+5 min
Sun 1 NovVught 22:13No data—
Sat 31 OctVught 22:150 min—
Fri 30 Oct— 22:090 min—
Thu 29 Oct— 22:030 min—
Wed 28 Oct— 22:050 min—
Tue 27 Oct— 22:090 min—
Mon 26 Oct— 22:04No data—
Sun 25 OctVught 22:16No data—
Sat 24 OctVught 22:12No data—
Fri 23 Oct— 22:07+1 min+1 min
Thu 22 Oct— 22:07No data—
Wed 21 Oct— 22:04No data—
Tue 20 Oct— 22:04No data—