Train NS 6548 Deurne – 's-Hertogenbosch

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

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 13:37 from Deurne · Thu 19 Nov

Next departure 13:37 today · Deurne
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 9 full · 10 partial · 10 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 15 full · 15 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Wed 11 Nov Max en route +6 min · last fix heading to Vught +6 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Vught +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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