Train NS 6558 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 16:07 from Deurne · Thu 19 Nov

Next departure 16:07 today · Deurne
On-time · 30 days
79%
19/24 runs under 3 min
RT coverage: 19 full · 5 partial · 5 no data
On-time · 90 days
86%
32/37 runs under 3 min
RT coverage: 31 full · 6 partial · 50 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: +4 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 +9 min · last fix heading to Vught +9 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Vught +5 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Vught +4 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Vught +3 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Vught +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 32
  • 3–10 min 14% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 83% W n=6
  • 100% T n=6
  • 100% F n=3
  • 67% S n=6
  • 80% S n=5

Stops and timetable

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

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