Train NS 6053 Den Haag Centraal – 's-Hertogenbosch

Den Haag Centraal 13:43 → 's-Hertogenbosch 15:32 Fri, Sat, Sun 1 h 49 min · 21 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 13:43 from Den Haag Centraal · Sun 15 Nov

Next departure 13:43 today · Den Haag Centraal
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 4 full · 4 partial · 3 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 11 full · 8 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Zaltbommel +4 min

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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=7
  • 100% S n=7
  • 67% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (21 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
13:43on time on time
13:47≈ on time ≈ on time
13:50≈ on time ≈ on time
13:55≈ on time ≈ on time
13:58≈ on time ≈ on time
14:00≈ on time ≈ on time
14:10 / 14:15≈ on time ≈ on time
14:18≈ on time ≈ on time
14:27 / 14:28≈ on time ≈ on time
14:34≈ on time ≈ on time
14:37≈ on time ≈ on time
14:40≈ on time ≈ on time
14:44 / 14:50≈ on time ≈ on time
14:52≈ on time ≈ on time
14:55≈ on time ≈ +1 min
14:58 / 14:59≈ on time ≈ +1 min
15:02≈ on time ≈ +1 min
15:08≈ on time ≈ +1 min
15:15 / 15:17≈ on time ≈ +1 min
15:23≈ on time ≈ +1 min
15:32on time +1 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
Sat 14 NovZaltbommel 15:37Partial coverage0 min—
Fri 13 NovZaltbommel 15:34Partial coverage+1 min+1 min
Fri 6 NovZaltbommel 15:37No data—
Sun 1 NovZaltbommel 15:38Partial coverage0 min—
Sat 31 OctZaltbommel 15:37Partial coverage0 min—
Fri 30 OctZaltbommel 15:37No data—
Sun 25 OctZaltbommel 15:38No data—
Sat 24 OctTiel Passewaaij 15:460 min—
Fri 23 OctTiel Passewaaij 15:480 min—
Sun 18 OctZaltbommel 15:40+4 min+4 min
Sat 17 OctZaltbommel 15:380 min—
Fri 16 OctZaltbommel 15:37No data—
Sun 11 OctZaltbommel 15:38Partial coverage+1 min+1 min
Sat 10 OctZaltbommel 15:37Partial coverage0 min—
Fri 9 OctZaltbommel 15:37Partial coverage0 min—
Mon 5 OctZaltbommel 15:37Partial coverage0 min—
Sun 4 OctZaltbommel 15:37No data—
Sat 3 OctUtrecht Centraal 01:08+1 min+1 min
Fri 2 OctUtrecht Centraal 17:430 min—
Sun 27 SeptZaltbommel 15:37No data—
Sat 26 SeptCulemborg 15:24No data—
Fri 25 SeptUtrecht Vaartsche Rijn 20:500 min+3 min
Mon 21 SeptUtrecht Vaartsche Rijn 17:560 min—
Sun 20 SeptZaltbommel 15:38No data—
Sat 19 SeptZaltbommel 15:37No data—
Fri 18 SeptZaltbommel 15:38No data—
Sun 13 SeptZaltbommel 15:37No data—
Sat 12 SeptZaltbommel 15:37No data—
Fri 11 SeptUtrecht Vaartsche Rijn 17:220 min—
Sun 6 SeptZaltbommel 15:38No data—