Train NS 6526 Deurne – 's-Hertogenbosch

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

✓ Today’s run finished

Today, last fix heading to Vught at 09:14 +2 min

  1. Deurne08:07
  2. Helmond08:16
  3. Helmond 't Hout08:19
  4. Eindhoven Centraal08:29
  5. Best08:44
  6. Vught08:58
  7. 's-Hertogenbosch09:03

Next service: tomorrow 08:07 from Deurne · Fri 20 Nov

Next departure 08:07 tomorrow · Deurne
On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 9 full · 14 partial · 7 no data
On-time · 90 days
89%
31/35 runs under 3 min
RT coverage: 15 full · 20 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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 +10 min · last fix heading to Vught +10 min
  • Mon 16 Nov Max en route +6 min · last fix heading to Vught +6 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Vught +4 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Vught +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 31
  • 3–10 min 9% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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