Train NS 6546 Deurne – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Vught at 14:13 +1 min

  1. Deurne13:07
  2. Helmond13:16
  3. Helmond 't Hout13:19
  4. Eindhoven Centraal13:29
  5. Best13:44
  6. Vught13:58
  7. 's-Hertogenbosch14:03

Next service: tomorrow 13:07 from Deurne · Thu 19 Nov

Next departure 13:07 tomorrow · Deurne
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 10 full · 12 partial · 8 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 16 full · 16 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: +2 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 +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 97% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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