Train NS 6525 's-Hertogenbosch – Deurne

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

✓ Today’s run finished

Today, last fix heading to Helmond Brouwhuis at 09:38 0 min

  1. 's-Hertogenbosch08:28
  2. Boxtel08:39
  3. Best08:46
  4. Eindhoven Centraal08:55
  5. Helmond 't Hout09:16
  6. Helmond Brouwhuis09:22
  7. Deurne09:28

Next service: tomorrow 08:28 from 's-Hertogenbosch · Mon 9 Nov

Next departure 08:28 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 11 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 64 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: +1 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

Worst days

  • Thu 8 Oct Max en route +4 min · last fix heading to Helmond Brouwhuis +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Helmond Brouwhuis +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 67% T n=3
  • 50% F n=2
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 23 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:28on time on time
08:33≈ on time ≈ on time
08:39≈ on time ≈ on time
08:46≈ on time ≈ +1 min
08:52≈ on time ≈ +1 min
08:55 / 09:06≈ on time ≈ +1 min
09:13≈ on time ≈ +1 min
09:16≈ on time ≈ +2 min
09:19≈ on time ≈ +2 min
09:22≈ on time ≈ +2 min
09:28on 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
Sun 8 NovHelmond Brouwhuis 09:38Partial coverage0 min+2 min
Sat 7 NovHelmond Brouwhuis 09:39+2 min+2 min
Fri 6 NovHelmond Brouwhuis 09:39No data—
Thu 5 NovHelmond Brouwhuis 09:38No data—
Wed 4 NovHelmond Brouwhuis 09:380 min—
Tue 3 NovHelmond Brouwhuis 09:390 min—
Mon 2 NovHelmond Brouwhuis 09:39No data—
Sun 1 NovEindhoven Strijp-S 09:07+1 min+2 min
Sat 31 OctEindhoven Strijp-S 09:060 min—
Fri 30 OctEindhoven Strijp-S 09:07No data—
Thu 29 OctHelmond Brouwhuis 09:370 min—
Wed 28 OctHelmond Brouwhuis 09:39No data—
Tue 27 OctHelmond Brouwhuis 09:38No data—
Mon 26 OctHelmond Brouwhuis 09:390 min—
Sun 25 OctHelmond Brouwhuis 09:38No data—
Sat 24 OctHelmond Brouwhuis 09:390 min—
Fri 23 OctHelmond Brouwhuis 09:39No data—
Thu 22 OctHelmond Brouwhuis 09:390 min—
Wed 21 OctHelmond Brouwhuis 09:400 min—
Tue 20 OctHelmond Brouwhuis 09:380 min—
Mon 19 OctHelmond Brouwhuis 09:380 min—
Sun 18 OctHelmond Brouwhuis 09:38+1 min+1 min
Sat 17 OctHelmond Brouwhuis 09:380 min—
Fri 16 OctHelmond Brouwhuis 09:370 min—
Thu 15 OctHelmond Brouwhuis 10:58No data—
Wed 14 OctHelmond Brouwhuis 09:39No data—
Tue 13 OctHelmond Brouwhuis 09:39No data—
Mon 12 OctHelmond Brouwhuis 09:380 min—
Sun 11 OctHelmond Brouwhuis 09:37+1 min+1 min
Sat 10 OctHelmond Brouwhuis 09:370 min—