Train NS 1760 Enschede – Den Haag Centraal
It has not run yet today
Last recorded run: Sunday 8 November 0 min
Next service: today 16:12 from Enschede · Mon 9 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
- Sun 11 Oct Max en route +15 min · last fix heading to Gouda +15 min
- Fri 23 Oct Max en route +8 min · last fix heading to Gouda +8 min
- Wed 28 Oct Max en route +4 min · last fix heading to Utrecht Centraal +4 min
- Mon 5 Oct Max en route +6 min · last fix heading to Utrecht Centraal +4 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 20
- 3–10 min 13% · 3
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 80% M n=5
- 100% T n=1
- 67% W n=3
- 100% T n=3
- 67% F n=3
- 100% S n=5
- 75% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 24 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 |
|---|---|---|---|
| 16:12 | on time | on time | |
| 16:17 | ≈ on time | ≈ on time | |
| 16:22 / 16:23 | ≈ on time | ≈ +1 min | |
| 16:34 / 16:35 | ≈ on time | ≈ +2 min | |
| 17:00 / 17:03 | ≈ on time | ≈ +2 min | |
| 17:13 / 17:14 | ≈ on time | ≈ +2 min | |
| 17:38 / 17:40 | ≈ on time | ≈ +3 min | |
| 17:53 / 17:58 | ≈ on time | ≈ +3 min | |
| 18:16 / 18:17 | ≈ on time | ≈ +4 min | |
| 18:25 | ≈ on time | ≈ +4 min | |
| 18:36 | on time | +4 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 |
|---|---|---|---|
| Sun 8 Nov | Lansingerland-Zoetermeer 18:39Partial coverage | 0 min | +1 min |
| Sat 7 Nov | Lansingerland-Zoetermeer 18:39 | +2 min | +3 min |
| Fri 6 Nov | Gouda 18:34 | 0 min | — |
| Thu 5 Nov | Utrecht Centraal 18:34 | 0 min | — |
| Wed 4 Nov | Utrecht Centraal 18:37 | 0 min | — |
| Tue 3 Nov | Utrecht Centraal 18:49 | No data | — |
| Mon 2 Nov | Gouda 18:34 | +2 min | +2 min |
| Sun 1 Nov | Gouda 18:34 | 0 min | — |
| Sat 31 Oct | Gouda 18:37 | +1 min | +1 min |
| Fri 30 Oct | Gouda 18:36 | No data | — |
| Thu 29 Oct | Utrecht Centraal 18:40 | 0 min | — |
| Wed 28 Oct | Utrecht Centraal 18:45 | +4 min | +4 min |
| Tue 27 Oct | Utrecht Centraal 18:37 | No data | — |
| Mon 26 Oct | Utrecht Centraal 18:12 | 0 min | — |
| Sun 25 Oct | Gouda 18:39 | No data | — |
| Sat 24 Oct | Gouda 18:52 | 0 min | — |
| Fri 23 Oct | Gouda 18:52 | +8 min | +8 min |
| Thu 22 Oct | Gouda 18:40 | No data | — |
| Wed 21 Oct | Gouda 18:36 | No data | — |
| Tue 20 Oct | Gouda 18:58 | No data | — |
| Mon 19 Oct | Amersfoort Centraal 17:54 | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 17:57 | 0 min | — |
| Sat 17 Oct | Gouda 18:36 | 0 min | — |
| Fri 16 Oct | — 18:36 | No data | — |
| Thu 15 Oct | Gouda 18:36 | No data | — |
| Wed 14 Oct | Gouda 18:36 | No data | — |
| Tue 13 Oct | Gouda 18:45 | No data | — |
| Mon 12 Oct | Gouda 18:53 | 0 min | — |
| Sun 11 Oct | Gouda 18:52 | +15 min | +15 min |
| Sat 10 Oct | Gouda 18:36 | 0 min | — |