Train NS 6541 's-Hertogenbosch – Deurne

's-Hertogenbosch 12:28 → Deurne 13:28 Daily 1 h 00 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 12:28 from 's-Hertogenbosch · Thu 5 Nov

Next departure 12:28 today · 's-Hertogenbosch
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 9 full · 8 partial · 12 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 10 full · 9 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Deurne, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 19 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
12:28on time on time
12:33≈ on time ≈ on time
12:39≈ on time ≈ on time
12:45≈ on time ≈ on time
12:51≈ on time ≈ on time
12:55 / 13:07≈ on time ≈ on time
13:13≈ on time ≈ on time
13:16≈ on time ≈ on time
13:20≈ on time ≈ on time
13:23≈ on time ≈ on time
13:28on time on time

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 4 NovHelmond Brouwhuis 13:38Partial coverage0 min—
Tue 3 NovHelmond Brouwhuis 13:38No data—
Mon 2 NovHelmond Brouwhuis 13:39Partial coverage0 min—
Sun 1 NovEindhoven Strijp-S 13:07No data—
Sat 31 OctEindhoven Strijp-S 13:060 min—
Fri 30 OctEindhoven Strijp-S 13:06No data—
Thu 29 OctHelmond Brouwhuis 13:410 min—
Wed 28 OctHelmond Brouwhuis 13:390 min—
Tue 27 OctHelmond Brouwhuis 13:380 min—
Mon 26 OctHelmond Brouwhuis 13:38No data—
Sun 25 OctHelmond Brouwhuis 13:38No data—
Sat 24 OctHelmond Brouwhuis 13:38Partial coverage0 min—
Fri 23 OctHelmond Brouwhuis 13:38No data—
Thu 22 OctHelmond Brouwhuis 13:39No data—
Wed 21 OctHelmond Brouwhuis 13:50No data—
Tue 20 OctHelmond Brouwhuis 13:38Partial coverage0 min—
Mon 19 OctHelmond Brouwhuis 13:38Partial coverage0 min—
Sun 18 OctHelmond Brouwhuis 13:370 min—
Sat 17 OctHelmond Brouwhuis 13:370 min—
Fri 16 OctHelmond Brouwhuis 13:37No data—
Thu 15 OctHelmond Brouwhuis 13:39No data—
Wed 14 OctHelmond Brouwhuis 13:38No data—
Tue 13 OctHelmond Brouwhuis 13:39No data—
Mon 12 OctHelmond Brouwhuis 13:39Partial coverage0 min—
Sun 11 OctHelmond Brouwhuis 13:38+1 min+2 min
Sat 10 OctHelmond Brouwhuis 13:370 min—
Fri 9 OctHelmond Brouwhuis 13:380 min—
Thu 8 OctHelmond Brouwhuis 13:38Partial coverage0 min—
Wed 7 OctHelmond Brouwhuis 13:39Partial coverage0 min—
Tue 6 OctHelmond Brouwhuis 13:38Partial coverage0 min—