Train NS 6063 Den Haag Centraal – 's-Hertogenbosch

Den Haag Centraal 16:13 → 's-Hertogenbosch 18:02 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 16:13 from Den Haag Centraal · Sun 15 Nov

Next departure 16:13 today · Den Haag Centraal
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 3 full · 5 partial · 3 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 12 full · 8 partial · 17 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 '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

  • Fri 6 Nov Max en route +3 min · last fix heading to Zaltbommel +3 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Zaltbommel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 75% F n=8
  • 100% S n=7
  • 100% S n=4

Stops and timetable

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

Last 90 days, 20 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
16:13on time on time
16:17≈ on time ≈ on time
16:20≈ on time ≈ on time
16:25≈ on time ≈ on time
16:27≈ on time ≈ on time
16:30≈ on time ≈ on time
16:40 / 16:45≈ on time ≈ on time
16:48≈ on time ≈ on time
16:57 / 16:58≈ on time ≈ on time
17:04≈ on time ≈ on time
17:07≈ on time ≈ on time
17:10≈ on time ≈ on time
17:14 / 17:20≈ on time ≈ on time
17:22≈ on time ≈ on time
17:25≈ on time ≈ on time
17:28 / 17:29≈ on time ≈ on time
17:32≈ on time ≈ on time
17:38≈ on time ≈ on time
17:45 / 17:47≈ on time ≈ on time
17:53≈ on time ≈ on time
18:02on time on time

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 18:07Partial coverage0 min—
Fri 13 NovZaltbommel 18:09Partial coverage+3 min+3 min
Fri 6 NovZaltbommel 18:08Partial coverage+3 min+3 min
Sun 1 NovZaltbommel 18:07Partial coverage0 min—
Sat 31 OctZaltbommel 18:07Partial coverage0 min—
Fri 30 OctZaltbommel 18:07No data—
Sun 25 OctZaltbommel 18:08No data—
Sat 24 OctTiel Passewaaij 18:160 min—
Fri 23 OctTiel Passewaaij 18:16No data—
Sun 18 OctZaltbommel 18:080 min—
Sat 17 OctZaltbommel 18:090 min—
Fri 16 OctZaltbommel 18:10No data—
Sun 11 OctZaltbommel 18:10Partial coverage+3 min+3 min
Sat 10 OctZaltbommel 18:08Partial coverage+1 min+1 min
Fri 9 OctZaltbommel 18:07Partial coverage+1 min+1 min
Mon 5 OctZaltbommel 18:070 min—
Sun 4 OctZaltbommel 18:08No data—
Sat 3 OctUtrecht Centraal 18:18−1 min+2 min
Fri 2 OctUtrecht Vaartsche Rijn 00:490 min+1 min
Sun 27 SeptZaltbommel 18:09No data—
Sat 26 SeptCulemborg 17:55No data—
Fri 25 SeptHouten 18:230 min—
Sun 20 SeptZaltbommel 18:07No data—
Sat 19 SeptZaltbommel 18:10No data—
Fri 18 SeptHouten 20:340 min+1 min
Sun 13 SeptUtrecht Vaartsche Rijn 00:490 min—
Sat 12 SeptUtrecht Leidsche Rijn 18:000 min—
Fri 11 SeptZaltbommel 18:05−1 min—
Sun 6 SeptZaltbommel 18:25No data—
Sat 5 SeptZaltbommel 18:07No data—