Train NS 6574 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:07 from Deurne · Sun 8 Nov

Next departure 20:07 today · Deurne
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 13 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 18 full · 2 partial · 33 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 +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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