Train NS 1780 Enschede – Utrecht Centraal

Enschede 21:15 → Utrecht Centraal 22:57 Daily 1 h 42 min · 7 stops NS (Nederlandse Spoorwegen)

Running now · updated 21:17

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 22:57 · 37 km/h

  1. Enschede21:15
  2. Hengelo21:22
  3. Almelo21:34
  4. Deventer22:00
  5. Apeldoorn22:13
  6. Amersfoort Centraal22:38
  7. Utrecht Centraal22:57

Today it is running no worse than usual: typical arrival delay is 0 min; 91% of the last 23 runs arrived on time.

On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 25 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Wed 7 Oct Max en route +6 min · last fix heading to — +6 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Amersfoort Centraal +4 min

Distribution · 90 days

25 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 75% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=3
  • 67% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 stops).

Last 90 days, 25 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.

StopSched.Usually 9 days in 10Today
21:15on time on time
21:22 / 21:23≈ on time ≈ on time
21:34 / 21:35≈ on time ≈ +1 min
22:00 / 22:03≈ on time ≈ +2 min
22:13 / 22:14≈ on time ≈ +2 min
22:38 / 22:40≈ on time ≈ +3 min
22:57on time +3 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

DateLast stopFinalMax
Thu 5 Nov— 21:140 min—
Wed 4 Nov— 23:390 min—
Tue 3 Nov— 22:590 min—
Mon 2 Nov— 23:420 min—
Sun 1 NovAmersfoort Centraal 22:540 min—
Sat 31 OctAmersfoort Centraal 23:440 min—
Fri 30 Oct— 22:580 min—
Thu 29 Oct— 22:580 min—
Wed 28 Oct— 22:580 min—
Tue 27 Oct— 22:590 min—
Mon 26 Oct— 23:41No data—
Sun 25 OctGouda 23:37No data—
Sat 24 OctAlmelo 23:380 min—
Fri 23 Oct— 23:39+2 min+3 min
Thu 22 Oct— 00:140 min—
Wed 21 Oct— 23:430 min—
Tue 20 Oct— 23:36No data—
Mon 19 Oct— 21:400 min—
Sun 18 OctAmersfoort Centraal 22:59+4 min+4 min
Sat 17 OctAmersfoort Centraal 23:04No data—
Fri 16 Oct— 23:42+1 min+1 min
Thu 15 Oct— 23:00No data—
Wed 14 Oct— 22:58No data—
Tue 13 Oct— 22:59No data—
Mon 12 Oct— 23:41+2 min+3 min
Sun 11 OctAmersfoort Centraal 22:580 min—
Sat 10 OctDeventer 23:420 min—
Fri 9 Oct— 22:580 min+4 min
Thu 8 Oct— 23:01+3 min+3 min
Wed 7 Oct— 23:00+6 min+6 min