Train NS 6550 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

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

Next departure 14:07 today · Deurne
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 8 full · 9 partial · 12 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 14 full · 14 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
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

  • Sun 8 Nov Max en route +15 min · last fix heading to Vught +15 min
  • Thu 8 Oct Max en route +11 min · last fix heading to Vught +11 min
  • Tue 17 Nov Max en route +6 min · last fix heading to Vught +6 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Vught +3 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 86% · 24
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

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

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