Train NS 6030 's-Hertogenbosch – Den Haag Centraal
✓ Today’s run finished
Today, last fix heading to Voorburg at 11:28 0 min
- 's-Hertogenbosch09:29
- Culemborg09:51
- Utrecht Vaartsche Rijn10:08
- Utrecht Terwijde10:20
- Gouda Goverwelle10:41
- Voorburg11:13
- Den Haag Centraal11:17
Next service: Friday 09:29 from 's-Hertogenbosch · Fri 20 Nov
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
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 11
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=2
- 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, 11 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 |
|---|---|---|---|
| 09:29 | on time | on time | |
| 09:39 | — | — | |
| 09:46 | — | — | |
| 09:51 | — | — | |
| 09:57 / 09:58 | — | — | |
| 10:01 | — | — | |
| 10:05 | — | — | |
| 10:08 | — | — | |
| 10:11 / 10:14 | — | — | |
| 10:18 | — | — | |
| 10:20 | — | — | |
| 10:24 | — | — | |
| 10:30 / 10:31 | — | — | |
| 10:41 | — | — | |
| 10:45 / 10:50 | — | — | |
| 10:59 | — | — | |
| 11:02 | — | — | |
| 11:05 | — | — | |
| 11:10 | — | — | |
| 11:13 | — | — | |
| 11: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 | Voorburg 11:28Partial coverage | 0 min | — |
| Sat 14 Nov | Voorburg 11:28Partial coverage | 0 min | — |
| Fri 13 Nov | Voorburg 11:28Partial coverage | 0 min | — |
| Fri 6 Nov | Voorburg 11:27 | No data | — |
| Sun 1 Nov | Voorburg 11:28Partial coverage | 0 min | — |
| Sat 31 Oct | Voorburg 11:28Partial coverage | 0 min | — |
| Fri 30 Oct | Voorburg 11:28 | No data | — |
| Sun 25 Oct | Voorburg 11:28 | No data | — |
| Sat 24 Oct | Voorburg 11:28 | 0 min | — |
| Fri 23 Oct | Voorburg 11:29 | No data | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 10:22 | 0 min | — |
| Sat 17 Oct | Voorburg 11:27Partial coverage | 0 min | — |
| Fri 16 Oct | Voorburg 11:28 | No data | — |
| Sun 11 Oct | Voorburg 11:27Partial coverage | 0 min | — |
| Sat 10 Oct | Voorburg 11:28Partial coverage | 0 min | — |
| Fri 9 Oct | Voorburg 11:28Partial coverage | 0 min | — |
| Mon 5 Oct | Voorburg 11:28 | No data | — |
| Sun 4 Oct | Voorburg 11:28 | No data | — |
| Sat 3 Oct | Voorburg 11:28 | No data | — |
| Fri 2 Oct | Voorburg 11:32 | No data | — |
| Sun 27 Sept | Voorburg 11:28 | No data | — |
| Sat 26 Sept | Voorburg 11:28 | No data | — |
| Fri 25 Sept | Voorburg 11:27 | No data | — |
| Sun 20 Sept | Voorburg 11:29 | No data | — |
| Sat 19 Sept | Voorburg 11:29 | No data | — |
| Fri 18 Sept | Voorburg 11:28 | No data | — |
| Sun 13 Sept | Voorburg 11:27 | No data | — |
| Sat 12 Sept | Voorburg 11:28 | No data | — |
| Fri 11 Sept | Voorburg 11:28 | No data | — |
| Sun 6 Sept | Voorburg 11:28 | No data | — |