Train NS 6544 Deurne – 's-Hertogenbosch

Deurne 12:37 → 's-Hertogenbosch 13:33 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Vught at 13:42 0 min

  1. Deurne12:37
  2. Helmond12:46
  3. Helmond 't Hout12:49
  4. Eindhoven Centraal12:59
  5. Best13:14
  6. Vught13:28
  7. 's-Hertogenbosch13:33

Next service: tomorrow 12:37 from Deurne · Wed 18 Nov

Next departure 12:37 tomorrow · Deurne
On-time · 30 days
84%
21/25 runs under 3 min
RT coverage: 20 full · 5 partial · 5 no data
On-time · 90 days
86%
31/36 runs under 3 min
RT coverage: 29 full · 7 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 6 Oct Max en route +14 min · last fix heading to Vught +14 min
  • Mon 16 Nov Max en route +10 min · last fix heading to Vught +10 min
  • Sun 15 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 +4 min · last fix heading to Vught +4 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 86% · 31
  • 3–10 min 11% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 86% T n=7
  • 100% W n=4
  • 75% T n=4
  • 75% F n=4
  • 100% S n=5
  • 80% S n=5

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
12:37on time on time
12:42≈ on time ≈ on time
12:46≈ on time ≈ +1 min
12:49≈ on time ≈ +1 min
12:51≈ on time ≈ +1 min
12:59 / 13:05≈ on time ≈ +2 min
13:09≈ on time ≈ +2 min
13:14≈ on time ≈ +3 min
13:21≈ on time ≈ +3 min
13:28≈ on time ≈ +4 min
13:33on 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
Tue 17 NovVught 13:42Partial coverage0 min—
Mon 16 NovVught 13:53+10 min+10 min
Sun 15 NovVught 13:45+6 min+6 min
Sat 14 NovVught 13:430 min—
Fri 13 NovVught 13:44+4 min+4 min
Thu 12 NovVught 13:44+5 min+5 min
Wed 11 NovVught 13:420 min—
Tue 10 NovVught 13:43Partial coverage+3 min+3 min
Mon 9 NovVught 13:420 min—
Sun 8 NovVught 13:42+1 min+1 min
Sat 7 NovVught 13:43+1 min—
Fri 6 NovVught 13:42No data—
Thu 5 NovVught 13:42No data—
Wed 4 NovVught 13:43+1 min—
Tue 3 NovVught 13:42Partial coverage0 min—
Mon 2 NovVught 13:590 min—
Sun 1 NovVught 13:440 min—
Sat 31 OctVught 13:44+1 min+1 min
Fri 30 OctVught 13:44No data—
Thu 29 Oct's-Hertogenbosch 13:590 min—
Wed 28 Oct's-Hertogenbosch 13:590 min—
Tue 27 Oct's-Hertogenbosch 13:590 min—
Mon 26 Oct's-Hertogenbosch 13:590 min—
Sun 25 OctVught 13:43No data—
Sat 24 OctVught 13:420 min—
Fri 23 OctVught 13:550 min—
Thu 22 OctVught 13:43Partial coverage0 min—
Wed 21 OctVught 13:42No data—
Tue 20 OctVught 13:55Partial coverage0 min—
Mon 19 OctVught 13:420 min—