Train NS 6538 Deurne → 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Friday 20 November +4 min

Next service: today 11:07 from Deurne · Sat 21 Nov

Next departure 11:07 today · Deurne
On-time · 30 days
71%
15/21 runs under 3 min
RT coverage: 17 full · 4 partial · 8 no data
On-time · 90 days
75%
24/32 runs under 3 min
RT coverage: 25 full · 7 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Thu 8 Oct Max en route +9 min · last fix heading to Vught +9 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Vught +5 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Vught +5 min
  • Fri 20 Nov Max en route +4 min · last fix heading to Vught +4 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Vught +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 24
  • 3–10 min 25% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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