Train NS 1786 Enschede – Utrecht Centraal

Enschede 22:45 → Utrecht Centraal 00:23 Daily 1 h 38 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 22:45 from Enschede · Thu 12 Nov

Next departure 22:45 today · Enschede
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 33 full · 0 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Fri 23 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=5
  • 100% T n=5
  • 75% F n=4
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 33 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
22:45on time on time
22:52 / 22:53≈ on time ≈ on time
23:04 / 23:05≈ on time ≈ on time
23:30 / 23:33≈ on time ≈ on time
23:43 / 23:44≈ on time ≈ on time
00:08 / 00:10≈ on time ≈ on time
00:23on time on time

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
Tue 10 Nov— 00:140 min+31 min
Mon 9 Nov— 01:100 min+2 min
Sun 8 NovAmersfoort Centraal 00:28+3 min+5 min
Sat 7 NovAlmelo 00:240 min—
Fri 6 Nov— 01:190 min—
Thu 5 Nov— 00:230 min—
Wed 4 Nov— 22:590 min—
Tue 3 Nov— 00:290 min—
Mon 2 Nov— 00:240 min—
Sun 1 NovAmersfoort Centraal 00:290 min+2 min
Sat 31 OctAlmelo 00:240 min—
Fri 30 Oct— 00:300 min—
Thu 29 Oct— 01:140 min—
Wed 28 Oct— 00:240 min—
Tue 27 Oct— 00:240 min—
Mon 26 Oct— 01:150 min—
Sun 25 OctGouda 01:140 min—
Sat 24 Oct— 01:210 min—
Fri 23 Oct— 01:13+4 min+5 min
Thu 22 Oct— 01:150 min—
Wed 21 Oct— 01:170 min—
Tue 20 Oct— 01:240 min—
Mon 19 Oct— 00:490 min+13 min
Thu 15 Oct— 00:240 min—
Wed 14 Oct— 00:250 min—
Tue 13 Oct— 01:120 min—
Sun 11 OctAmersfoort Centraal 00:240 min—
Sat 10 Oct— 01:260 min—
Fri 9 Oct— 00:240 min—
Thu 8 Oct— 01:120 min—