Train NS 6519 's-Hertogenbosch – Deurne

's-Hertogenbosch 06:58 → Deurne 07:57 Mon, Tue, Wed, Thu, Fri, Sat 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Helmond Brouwhuis at 08:08 No data

  1. 's-Hertogenbosch06:58
  2. Boxtel07:09
  3. Best07:15
  4. Eindhoven Centraal07:25
  5. Helmond 't Hout07:45
  6. Helmond Brouwhuis07:52
  7. Deurne07:57

Next service: tomorrow 06:58 from 's-Hertogenbosch · Fri 6 Nov

Next departure 06:58 tomorrow · 's-Hertogenbosch
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 12 full · 12 partial · 2 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 12 full · 13 partial · 52 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 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
06:58on time on time
07:02≈ on time ≈ on time
07:09≈ on time ≈ on time
07:15≈ on time ≈ +1 min
07:21≈ on time ≈ +1 min
07:25 / 07:36≈ on time ≈ +1 min
07:42≈ on time ≈ +1 min
07:45≈ on time ≈ +1 min
07:49≈ on time ≈ +2 min
07:52≈ on time ≈ +2 min
07:57on 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 5 NovHelmond Brouwhuis 08:08No data—
Wed 4 NovHelmond Brouwhuis 08:07Partial coverage0 min—
Tue 3 NovHelmond Brouwhuis 08:08Partial coverage0 min—
Mon 2 NovHelmond Brouwhuis 08:09No data—
Sat 31 OctEindhoven Strijp-S 07:36+1 min+1 min
Fri 30 OctEindhoven Strijp-S 07:38+2 min+2 min
Thu 29 OctHelmond Brouwhuis 08:070 min—
Wed 28 OctHelmond Brouwhuis 08:120 min—
Tue 27 OctHelmond Brouwhuis 08:080 min—
Mon 26 OctHelmond Brouwhuis 08:080 min—
Sat 24 OctHelmond Brouwhuis 08:10+2 min+2 min
Fri 23 OctHelmond Brouwhuis 08:110 min—
Thu 22 OctHelmond Brouwhuis 08:080 min—
Wed 21 OctHelmond Brouwhuis 08:080 min—
Tue 20 OctHelmond Brouwhuis 08:060 min—
Mon 19 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Sat 17 OctHelmond Brouwhuis 08:08Partial coverage+1 min+2 min
Fri 16 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Thu 15 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Wed 14 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Tue 13 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Mon 12 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Sat 10 OctHelmond Brouwhuis 08:070 min—
Fri 9 OctHelmond Brouwhuis 08:08Partial coverage0 min—
Thu 8 OctHelmond Brouwhuis 08:09Partial coverage+2 min+2 min
Wed 7 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Tue 6 OctHelmond Brouwhuis 08:07Partial coverage0 min—
Mon 5 OctHelmond Brouwhuis 08:08No data—
Sat 3 OctHelmond Brouwhuis 08:08No data—
Fri 2 OctHelmond Brouwhuis 08:07No data—