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: Thursday 5 November 0 min

Next service: today 16:07 from Deurne · Fri 6 Nov

Next departure 16:07 today · Deurne
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 13 full · 8 partial · 8 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 15 full · 9 partial · 63 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

Worst days

  • Sat 24 Oct Max en route +3 min · last fix heading to Vught +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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 ≈ on time
16:19≈ on time ≈ on time
16:21≈ on time ≈ on time
16:29 / 16:35≈ on time ≈ on time
16:39≈ on time ≈ +1 min
16:44≈ on time ≈ +1 min
16:51≈ on time ≈ +1 min
16:58≈ on time ≈ +1 min
17: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
Thu 5 NovVught 17:12Partial coverage0 min—
Wed 4 NovVught 17:120 min—
Tue 3 NovVught 17:12Partial coverage0 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:13+3 min+3 min
Fri 23 OctVught 17:13No data—
Thu 22 OctVught 17:14Partial coverage0 min—
Wed 21 OctVught 17:150 min—
Tue 20 OctVught 17:13Partial coverage0 min—
Mon 19 OctVught 17:13Partial coverage0 min—
Sun 18 OctVught 17:120 min+1 min
Sat 17 OctVught 17:140 min—
Fri 16 OctVught 17:13No data—
Thu 15 OctVught 17:12Partial coverage0 min—
Wed 14 OctVught 17:16No data—
Tue 13 OctVught 17:13No data—
Mon 12 OctVught 17:12Partial coverage0 min—
Sun 11 OctVught 17:13+1 min—
Sat 10 OctVught 17:13+1 min+1 min
Fri 9 OctVught 17:120 min—
Thu 8 OctVught 17:12Partial coverage0 min—
Wed 7 OctVught 17:120 min—