Train NS 6540 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 11:37 from Deurne · Tue 17 Nov

Next departure 11:37 today · Deurne
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 10 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 16 full · 12 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 13 Nov 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 96% · 27
  • 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=4
  • 100% W n=4
  • 100% T n=3
  • 67% F n=3
  • 100% S n=5
  • 100% S n=5

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