Train NS 6556 Deurne – 's-Hertogenbosch

Deurne 15:37 → 's-Hertogenbosch 16:33 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 15:37 from Deurne · Sat 7 Nov

Next departure 15:37 today · Deurne
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 16 full · 8 partial · 5 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 18 full · 10 partial · 58 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

  • Tue 6 Oct Max en route +17 min · last fix heading to Eindhoven Centraal +17 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
15:37on time on time
15:42≈ on time ≈ on time
15:46≈ on time ≈ on time
15:49≈ on time ≈ on time
15:51≈ on time ≈ on time
15:59 / 16:05≈ on time ≈ on time
16:09≈ on time ≈ +1 min
16:14≈ on time ≈ +1 min
16:21≈ on time ≈ +1 min
16:28≈ on time ≈ +1 min
16:33on 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
Fri 6 NovVught 16:42No data—
Thu 5 NovVught 16:42Partial coverage0 min—
Wed 4 NovVught 16:420 min—
Tue 3 NovVught 16:39Partial coverage0 min—
Mon 2 NovVught 16:420 min—
Sun 1 NovVught 16:430 min—
Sat 31 OctVught 16:430 min—
Fri 30 OctVught 16:42No data—
Thu 29 Oct's-Hertogenbosch 16:580 min—
Wed 28 Oct's-Hertogenbosch 16:580 min—
Tue 27 Oct's-Hertogenbosch 16:580 min—
Mon 26 Oct's-Hertogenbosch 16:580 min—
Sun 25 OctVught 16:42No data—
Sat 24 OctVught 16:43Partial coverage0 min—
Fri 23 OctVught 16:42Partial coverage0 min—
Thu 22 OctVught 16:43Partial coverage0 min—
Wed 21 OctVught 16:42No data—
Tue 20 OctVught 16:42Partial coverage0 min—
Mon 19 OctVught 16:430 min—
Sun 18 OctVught 16:43+1 min—
Sat 17 OctVught 16:43No data—
Fri 16 OctVught 16:430 min—
Thu 15 OctVught 16:42Partial coverage0 min—
Wed 14 OctVught 16:430 min—
Tue 13 OctVught 16:43Partial coverage0 min—
Mon 12 OctVught 16:43+1 min+2 min
Sun 11 OctVught 16:43+1 min+1 min
Sat 10 OctVught 16:46+3 min+3 min
Fri 9 OctVught 16:43+1 min—
Thu 8 OctVught 16:44Partial coverage+2 min+2 min