Train NS 6581 's-Hertogenbosch – Deurne

's-Hertogenbosch 22:28 → Deurne 23:27 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 23:10

Heading to Deurne +2 min

Estimated arrival at Deurne 23:29 23:27 · 56 km/h

  1. 's-Hertogenbosch22:28
  2. Boxtel22:39
  3. Best22:45
  4. Eindhoven Centraal22:55
  5. Helmond 't Hout23:15
  6. Helmond23:19
  7. Deurne23:27

Today it is running worse than usual: typical arrival delay is 0 min; 91% of the last 23 runs arrived on time.

On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 6 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 34 full · 1 partial · 21 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 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

  • Fri 13 Nov Max en route +23 min · last fix heading to — +23 min
  • Mon 9 Nov Max en route +9 min · last fix heading to — +8 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Eindhoven Strijp-S +4 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 91% · 32
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 86% F n=7
  • 100% S n=4
  • 80% 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 10Today
22:28on time on time
22:32≈ on time ≈ on time
22:39≈ on time ≈ +1 min
22:45≈ on time ≈ +1 min
22:51≈ on time ≈ +1 min
22:55 / 23:06≈ on time ≈ +1 min
23:12≈ on time ≈ +2 min
23:15≈ on time ≈ +2 min
23:19≈ on time ≈ +2 min
23:22≈ on time ≈ +3 min
23:27on time +3 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
Fri 20 Nov— 23:09+1 min+1 min
Thu 19 Nov— 22:57+1 min+1 min
Wed 18 Nov— 22:59+3 min+3 min
Tue 17 Nov— 23:280 min—
Sun 15 NovEindhoven Strijp-S 23:07+1 min+2 min
Sat 14 NovEindhoven Strijp-S 23:29Partial coverage0 min—
Fri 13 Nov— 00:09+23 min+23 min
Thu 12 Nov— 22:570 min—
Wed 11 Nov— 22:540 min—
Tue 10 Nov— 23:29+2 min+2 min
Mon 9 Nov— 23:34+8 min+9 min
Sun 8 NovEindhoven Strijp-S 23:040 min—
Sat 7 NovHelmond Brouwhuis 23:340 min—
Fri 6 Nov— 23:29+1 min+1 min
Thu 5 Nov— 22:59No data—
Wed 4 Nov— 22:540 min—
Tue 3 Nov— 23:34No data—
Mon 2 Nov— 23:29+1 min+1 min
Sun 1 NovEindhoven Strijp-S 23:08+2 min+3 min
Sat 31 OctEindhoven Strijp-S 23:050 min—
Fri 30 Oct— 22:580 min—
Thu 29 Oct— 22:580 min+2 min
Wed 28 Oct— 23:010 min—
Tue 27 Oct— 23:310 min—
Mon 26 Oct— 23:29No data—
Sun 25 OctEindhoven Strijp-S 23:08No data—
Sat 24 OctBoxtel 23:33No data—
Fri 23 Oct— 23:32+1 min+1 min
Thu 22 Oct— 22:57No data—
Wed 21 Oct— 22:57No data—