Train NS 6034 's-Hertogenbosch – Den Haag Centraal

's-Hertogenbosch 10:29 → Den Haag Centraal 12:17 Fri, Sat, Sun 1 h 48 min · 21 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Voorburg at 12:28 0 min

  1. 's-Hertogenbosch10:29
  2. Culemborg10:51
  3. Utrecht Vaartsche Rijn11:08
  4. Utrecht Terwijde11:20
  5. Gouda Goverwelle11:41
  6. Voorburg12:13
  7. Den Haag Centraal12:17

Next service: Friday 10:29 from 's-Hertogenbosch · Fri 20 Nov

Next departure 10:29 Friday · 's-Hertogenbosch
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 3 full · 7 partial · 2 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 3 full · 11 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Den Haag Centraal, 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 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
  • 100% F n=4
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 14 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
10:29on time on time
10:39— —
10:46— —
10:51— —
10:57 / 10:58— —
11:01— —
11:05— —
11:08— —
11:11 / 11:14— —
11:18— —
11:20— —
11:24— —
11:30 / 11:31— —
11:41— —
11:45 / 11:50— —
11:59— —
12:02— —
12:05— —
12:10— —
12:13— —
12:17— —

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
Sun 15 NovVoorburg 12:28Partial coverage0 min—
Sat 14 NovVoorburg 12:28Partial coverage0 min—
Fri 13 NovVoorburg 12:28Partial coverage0 min—
Fri 6 NovVoorburg 12:28No data—
Sun 1 NovVoorburg 12:28Partial coverage0 min—
Sat 31 OctVoorburg 12:28Partial coverage0 min—
Fri 30 OctVoorburg 12:28Partial coverage0 min—
Sun 25 OctVoorburg 12:28No data—
Sat 24 OctVoorburg 12:280 min—
Fri 23 OctVoorburg 12:280 min—
Sun 18 OctUtrecht Vaartsche Rijn 11:220 min—
Sat 17 OctVoorburg 12:28Partial coverage0 min—
Fri 16 OctVoorburg 12:28No data—
Sun 11 OctVoorburg 12:28Partial coverage0 min+1 min
Sat 10 OctVoorburg 12:27Partial coverage0 min—
Fri 9 OctVoorburg 12:28Partial coverage0 min—
Mon 5 OctVoorburg 12:30Partial coverage+3 min+3 min
Sun 4 OctVoorburg 12:27No data—
Sat 3 OctVoorburg 12:29No data—
Fri 2 OctVoorburg 12:27No data—
Sun 27 SeptVoorburg 12:28No data—
Sat 26 SeptVoorburg 12:28No data—
Fri 25 SeptVoorburg 12:28No data—
Sun 20 SeptVoorburg 12:28No data—
Sat 19 SeptVoorburg 12:30No data—
Fri 18 SeptVoorburg 12:28No data—
Sun 13 SeptVoorburg 12:28No data—
Sat 12 SeptVoorburg 12:29No data—
Fri 11 SeptVoorburg 12:28No data—
Sun 6 SeptVoorburg 12:27No data—