Train NS 6570 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Saturday 7 November +3 min

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

Next departure 19:07 today · Deurne
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 9 full · 3 partial · 16 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 14 full · 3 partial · 42 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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 50% W n=2
  • 100% T n=1
  • 67% F n=3
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

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