Train NS 6522 Deurne – 's-Hertogenbosch

Deurne 07:07 → 's-Hertogenbosch 08:03 Mon, Tue, Wed, Thu, Fri, Sat 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 07:07 from Deurne · Thu 19 Nov

Next departure 07:07 today · Deurne
On-time · 30 days
74%
17/23 runs under 3 min
RT coverage: 9 full · 14 partial · 2 no data
On-time · 90 days
83%
30/36 runs under 3 min
RT coverage: 14 full · 22 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 +13 min · last fix heading to Vught +13 min
  • Mon 16 Nov Max en route +9 min · last fix heading to Vught +9 min
  • Sat 7 Nov Max en route +6 min · last fix heading to Vught +6 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Vught +5 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Vught +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 30
  • 3–10 min 14% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 86% T n=7
  • 86% W n=7
  • 80% T n=5
  • 80% F n=5
  • 83% S n=6
  • — S n=0

Stops and timetable

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

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