Train NS 1780 Enschede – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 21:15 from Enschede · Fri 20 Nov

Next departure 21:15 today · Enschede
On-time · 30 days
85%
23/27 runs under 3 min
RT coverage: 25 full · 2 partial · 2 no data
On-time · 90 days
82%
32/39 runs under 3 min
RT coverage: 37 full · 2 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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 17 Nov Max en route +6 min · last fix heading to — +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Thu 12 Nov 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

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

  • Early 0% · 0
  • On time 82% · 32
  • 3–10 min 18% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 40% T n=5
  • 67% W n=6
  • 83% T n=6
  • 100% F n=6
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 39 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 10
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 +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

DateLast stopFinalMax
Thu 19 Nov— 22:580 min—
Wed 18 Nov— 22:58+3 min+3 min
Tue 17 Nov— 22:58+5 min+6 min
Mon 16 NovAlmelo 22:590 min—
Sun 15 NovAmersfoort Centraal 22:59Partial coverage+2 min+2 min
Sat 14 NovAmersfoort Centraal 23:44Partial coverage0 min—
Fri 13 Nov— 23:470 min—
Thu 12 Nov— 23:44+4 min+4 min
Wed 11 Nov— 22:580 min—
Tue 10 Nov— 22:59+4 min+4 min
Mon 9 Nov— 22:59+1 min—
Sun 8 NovAmersfoort Centraal 22:590 min—
Sat 7 NovAmersfoort Centraal 22:59+1 min—
Fri 6 Nov— 23:470 min+2 min
Thu 5 Nov— 23:290 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—