Train NS 6050 's-Hertogenbosch – Den Haag Centraal
Running now · updated 15:39
Heading to Den Haag Centraal 0 min
Estimated arrival at Den Haag Centraal 16:17 · 139 km/h
- 's-Hertogenbosch14:29
- Culemborg14:51
- Utrecht Vaartsche Rijn15:08
- Utrecht Terwijde15:20
- Gouda Goverwelle15:41
- Zoetermeer16:05
- Den Haag Centraal16:17
Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 10 runs arrived on time.
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
Worst days
- Sun 18 Oct Max en route +6 min · last fix heading to Utrecht Vaartsche Rijn +5 min
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 93% · 13
- 3–10 min 7% · 1
- 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
- 75% 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.
| Stop | Sched. | Usually | 9 days in 10 | Today |
|---|---|---|---|---|
| 14:29 | on time | on time | ||
| 14:39 | — | — | ||
| 14:46 | — | — | ||
| 14:51 | — | — | ||
| 14:57 / 14:58 | — | — | ||
| 15:01 | — | — | ||
| 15:05 | — | — | ||
| 15:08 | — | — | ||
| 15:11 / 15:14 | — | — | ||
| 15:18 | — | — | ||
| 15:20 | — | — | ||
| 15:24 | — | — | ||
| 15:30 / 15:31 | — | — | ||
| 15:41 | — | — | ||
| 15:45 / 15:50 | — | — | ||
| 15:59 | — | — | ||
| 16:02 | — | — | ||
| 16:05 | — | — | ||
| 16:10 | — | — | ||
| 16:13 | — | — | ||
| 16: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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 15 Nov | Woerden 15:35Partial coverage | 0 min | — |
| Sat 14 Nov | Voorburg 16:27Partial coverage | 0 min | — |
| Fri 13 Nov | Voorburg 16:28Partial coverage | 0 min | — |
| Fri 6 Nov | Voorburg 16:27 | No data | — |
| Sun 1 Nov | Voorburg 16:28Partial coverage | 0 min | — |
| Sat 31 Oct | Voorburg 16:27Partial coverage | 0 min | — |
| Fri 30 Oct | Voorburg 16:27Partial coverage | 0 min | — |
| Sun 25 Oct | Voorburg 16:28 | No data | — |
| Sat 24 Oct | Voorburg 16:27 | 0 min | — |
| Fri 23 Oct | Voorburg 16:28 | 0 min | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 15:27 | +5 min | +6 min |
| Sat 17 Oct | Voorburg 16:48Partial coverage | 0 min | — |
| Fri 16 Oct | Voorburg 16:30 | No data | — |
| Sun 11 Oct | Voorburg 16:28Partial coverage | 0 min | — |
| Sat 10 Oct | Voorburg 16:29Partial coverage | +2 min | +2 min |
| Fri 9 Oct | Voorburg 16:27Partial coverage | 0 min | — |
| Mon 5 Oct | Voorburg 16:28Partial coverage | 0 min | — |
| Sun 4 Oct | Voorburg 16:27 | No data | — |
| Sat 3 Oct | Voorburg 16:27 | No data | — |
| Fri 2 Oct | Voorburg 16:28 | No data | — |
| Sun 27 Sept | Voorburg 16:28 | No data | — |
| Sat 26 Sept | Voorburg 16:27 | No data | — |
| Fri 25 Sept | Voorburg 16:28 | No data | — |
| Sun 20 Sept | Voorburg 16:28 | No data | — |
| Sat 19 Sept | Voorburg 16:29 | No data | — |
| Fri 18 Sept | Voorburg 16:29 | No data | — |
| Sun 13 Sept | Voorburg 16:28 | No data | — |
| Sat 12 Sept | Voorburg 16:28 | No data | — |
| Fri 11 Sept | Voorburg 16:28 | No data | — |
| Sun 6 Sept | Voorburg 16:28 | No data | — |