Train NS 6562 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 17:07 from Deurne · Tue 10 Nov

Next departure 17:07 today · Deurne
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 10 full · 3 partial · 16 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 14 full · 6 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=2
  • 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, 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
17:07on time on time
17:12≈ on time ≈ on time
17:16≈ on time ≈ on time
17:19≈ on time ≈ on time
17:21≈ on time ≈ on time
17:29 / 17:35≈ on time ≈ on time
17:39≈ on time ≈ on time
17:44≈ on time ≈ on time
17:51≈ on time ≈ on time
17:58≈ on time ≈ +1 min
18:03on time +1 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
Mon 9 NovVught 18:12Partial coverage+1 min+1 min
Sun 8 NovVught 18:120 min—
Sat 7 NovVught 18:120 min—
Fri 6 NovVught 18:12+1 min—
Thu 5 NovVught 18:09No data—
Wed 4 NovVught 18:12No data—
Tue 3 NovVught 18:12No data—
Mon 2 NovVught 18:12No data—
Sun 1 NovVught 18:14+1 min—
Sat 31 OctVught 18:130 min—
Fri 30 OctVught 18:12No data—
Thu 29 OctVught 18:28No data—
Wed 28 OctVught 18:270 min—
Tue 27 OctVught 18:28No data—
Mon 26 OctVught 18:270 min—
Sun 25 OctVught 18:13No data—
Sat 24 OctVught 18:15Partial coverage0 min—
Fri 23 OctVught 18:12No data—
Thu 22 OctVught 18:12No data—
Wed 21 OctVught 18:12No data—
Tue 20 OctVught 18:120 min—
Mon 19 OctVught 18:120 min—
Sun 18 OctVught 18:120 min—
Sat 17 OctVught 18:12No data—
Fri 16 OctVught 18:12No data—
Thu 15 OctVught 18:12No data—
Wed 14 OctVught 18:12No data—
Tue 13 OctVught 18:12No data—
Mon 12 OctVught 18:12Partial coverage0 min—
Sun 11 OctVught 18:120 min—