Train NS 6016 Utrecht Centraal – Den Haag Centraal
✓ Today’s run finished
Today, last fix heading to Voorburg at 07:54 0 min
- Utrecht Centraal06:44
- Utrecht Terwijde06:50
- Woerden07:00
- Gouda07:15
- Zoetermeer Oost07:30
- Voorburg07:40
- Den Haag Centraal07:45
Next service: Monday 06:44 from Utrecht Centraal · Mon 16 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
Worst days
- Mon 21 Sept Max en route +34 min · last fix heading to Voorburg +34 min
- Tue 10 Nov Max en route +8 min · last fix heading to Voorburg +8 min
- Thu 12 Nov Max en route +4 min · last fix heading to Voorburg +4 min
- Tue 18 Aug Max en route +3 min · last fix heading to Den Haag Ypenburg +3 min
Distribution · 90 days
69 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 7% · 5
- On time 87% · 60
- 3–10 min 4% · 3
- 10–30 min 0% · 0
- 30+ min 1% · 1
On-time by weekday
- 92% M n=12
- 85% T n=13
- 100% W n=11
- 92% T n=13
- 100% F n=11
- 100% S n=9
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 69 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 |
|---|---|---|---|
| 06:44 | on time | on time | |
| 06:48 | ≈ on time | ≈ on time | |
| 06:50 | ≈ on time | ≈ on time | |
| 06:54 | ≈ on time | ≈ on time | |
| 07:00 / 07:01 | ≈ on time | ≈ +1 min | |
| 07:11 | ≈ on time | ≈ +1 min | |
| 07:15 / 07:17 | ≈ on time | ≈ +1 min | |
| 07:26 | ≈ on time | ≈ +1 min | |
| 07:30 | ≈ on time | ≈ +1 min | |
| 07:32 | ≈ on time | ≈ +1 min | |
| 07:37 | ≈ on time | ≈ +2 min | |
| 07:40 | ≈ on time | ≈ +2 min | |
| 07:45 | on time | +2 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 14 Nov | Voorburg 07:54Partial coverage | 0 min | — |
| Fri 13 Nov | Voorburg 07:58 | +1 min | +1 min |
| Thu 12 Nov | Voorburg 07:59 | +4 min | +4 min |
| Wed 11 Nov | Voorburg 07:57 | 0 min | — |
| Tue 10 Nov | Voorburg 08:03 | +8 min | +8 min |
| Mon 9 Nov | Voorburg 07:58 | 0 min | — |
| Fri 6 Nov | Voorburg 07:58 | No data | — |
| Thu 5 Nov | Voorburg 07:58 | 0 min | — |
| Wed 4 Nov | Voorburg 07:59 | +1 min | +1 min |
| Tue 3 Nov | Voorburg 08:17 | 0 min | — |
| Mon 2 Nov | Voorburg 07:58 | No data | — |
| Sat 31 Oct | Voorburg 07:55Partial coverage | 0 min | +2 min |
| Fri 30 Oct | Voorburg 07:58 | 0 min | — |
| Thu 29 Oct | Voorburg 08:03 | 0 min | — |
| Wed 28 Oct | Voorburg 07:57 | 0 min | — |
| Tue 27 Oct | Voorburg 07:58 | 0 min | — |
| Mon 26 Oct | Voorburg 07:58 | 0 min | — |
| Sat 24 Oct | Voorburg 07:58 | 0 min | — |
| Fri 23 Oct | Voorburg 07:57 | 0 min | — |
| Thu 22 Oct | Voorburg 08:00 | 0 min | — |
| Wed 21 Oct | Voorburg 08:01 | 0 min | — |
| Tue 20 Oct | Voorburg 08:00 | 0 min | — |
| Mon 19 Oct | Voorburg 08:04 | 0 min | — |
| Sat 17 Oct | Voorburg 07:56Partial coverage | 0 min | — |
| Fri 16 Oct | Voorburg 07:58 | 0 min | — |
| Thu 15 Oct | Voorburg 07:59 | 0 min | — |
| Wed 14 Oct | Voorburg 07:58 | 0 min | — |
| Tue 13 Oct | Voorburg 07:59 | 0 min | — |
| Mon 12 Oct | Voorburg 07:57 | 0 min | — |
| Sat 10 Oct | Voorburg 07:55Partial coverage | 0 min | — |