Train NS 1756 Enschede – Den Haag Centraal
✓ Today’s run finished
Today, last fix heading to Lansingerland-Zoetermeer at 17:39 +2 min
- Enschede15:15
- Almelo15:34
- Deventer16:00
- Amersfoort Centraal16:38
- Utrecht Centraal16:53
- Lansingerland-Zoetermeer17:25
- Den Haag Centraal17:36
Next service: tomorrow 15:15 from Enschede · Sun 8 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
- Tue 6 Oct Max en route +7 min · last fix heading to Gouda +7 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 96% · 23
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 50% T n=2
- 100% W n=3
- 100% T n=4
- 100% F n=4
- 100% S n=5
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 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 |
|---|---|---|---|
| 15:15 | on time | on time | |
| 15:22 / 15:23 | ≈ on time | ≈ on time | |
| 15:34 / 15:35 | ≈ on time | ≈ on time | |
| 16:00 / 16:03 | ≈ on time | ≈ on time | |
| 16:13 / 16:14 | ≈ on time | ≈ on time | |
| 16:38 / 16:40 | ≈ on time | ≈ +1 min | |
| 16:53 / 16:58 | ≈ on time | ≈ +1 min | |
| 17:16 / 17:17 | ≈ on time | ≈ +1 min | |
| 17:25 | ≈ on time | ≈ +1 min | |
| 17:36 | on time | +1 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 7 Nov | Lansingerland-Zoetermeer 17:39Partial coverage | +2 min | +2 min |
| Fri 6 Nov | Gouda 17:37 | +1 min | — |
| Thu 5 Nov | Gouda 17:34 | 0 min | — |
| Wed 4 Nov | Gouda 17:53 | 0 min | — |
| Tue 3 Nov | Gouda 17:34 | No data | — |
| Mon 2 Nov | Gouda 17:34 | No data | — |
| Sun 1 Nov | Gouda 17:39 | +1 min | +3 min |
| Sat 31 Oct | Gouda 17:36 | 0 min | — |
| Fri 30 Oct | Gouda 17:31 | 0 min | — |
| Thu 29 Oct | Almelo 17:37 | 0 min | — |
| Wed 28 Oct | Gouda 17:52 | No data | — |
| Tue 27 Oct | Gouda 17:49 | No data | — |
| Mon 26 Oct | Gouda 17:39 | No data | — |
| Sun 25 Oct | Gouda 17:36 | No data | — |
| Sat 24 Oct | Gouda 17:36 | 0 min | — |
| Fri 23 Oct | Gouda 17:38 | 0 min | — |
| Thu 22 Oct | Gouda 17:35 | 0 min | — |
| Wed 21 Oct | Gouda 17:38 | No data | — |
| Tue 20 Oct | Gouda 17:38 | 0 min | — |
| Mon 19 Oct | Amersfoort Centraal 16:55 | 0 min | — |
| Sun 18 Oct | Amersfoort Centraal 16:55 | 0 min | — |
| Sat 17 Oct | Gouda 17:41 | 0 min | — |
| Thu 15 Oct | Gouda 17:36 | No data | — |
| Wed 14 Oct | Gouda 17:40 | 0 min | — |
| Tue 13 Oct | Gouda 17:53 | No data | — |
| Mon 12 Oct | Gouda 17:37 | 0 min | — |
| Sun 11 Oct | Gouda 17:36 | 0 min | — |
| Sat 10 Oct | Gouda 17:36 | 0 min | — |
| Fri 9 Oct | Gouda 17:36 | 0 min | — |
| Thu 8 Oct | Gouda 17:37 | +1 min | — |