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