Train NS 1718 Enschede → Utrecht Centraal

Enschede 05:45 → Utrecht Centraal 07:23 Mon, Tue, Wed, Thu, Fri, Sat 1 h 38 min · 7 stops NS (Nederlandse Spoorwegen)

Running now · updated 06:47

Position estimated from the timetable

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 07:23 · 100 km/h

  1. Enschede05:45
  2. Hengelo05:52
  3. Almelo06:04
  4. Deventer06:30
  5. Apeldoorn06:43
  6. Amersfoort Centraal07:08
  7. Utrecht Centraal07:23

Today it is running no worse than usual: typical arrival delay is +1 min; 92% of the last 25 runs arrived on time.

On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 23 full · 2 partial · 1 no data
On-time · 90 days
81%
57/70 runs under 3 min
RT coverage: 67 full · 3 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
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

  • Thu 8 Oct Max en route +18 min · last fix heading to Gouda +18 min
  • Tue 6 Oct Max en route +16 min · last fix heading to Amersfoort Centraal +16 min
  • Tue 8 Sept Max en route +10 min · last fix heading to Utrecht Centraal +10 min
  • Fri 25 Sept Max en route +9 min · last fix heading to Utrecht Centraal +8 min
  • Fri 2 Oct Max en route +7 min · last fix heading to Utrecht Centraal +7 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 79% · 55
  • 3–10 min 14% · 10
  • 10–30 min 4% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 83% T n=12
  • 100% W n=12
  • 67% T n=12
  • 50% F n=12
  • 100% S n=9
  • — S n=0

Stops and timetable

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

Last 90 days, 70 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
05:45on time on time
05:52 / 05:53≈ on time ≈ on time
06:04 / 06:05≈ on time ≈ +1 min
06:30 / 06:33≈ on time ≈ +3 min
06:43 / 06:44≈ on time ≈ +3 min
07:08 / 07:10≈ on time ≈ +5 min
07:23on time +6 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
Sat 21 NovApeldoorn 06:44Partial coverage0 min—
Fri 20 NovGouda 08:19+6 min+8 min
Thu 19 NovGouda 08:09+2 min+3 min
Wed 18 NovGouda 08:04+1 min+1 min
Tue 17 NovGouda 08:09+2 min+3 min
Mon 16 NovGouda 08:14+5 min+5 min
Sat 14 NovAmersfoort Centraal 08:09Partial coverage+1 min+2 min
Fri 13 NovGouda 08:09+1 min+2 min
Thu 12 NovGouda 08:13+2 min+2 min
Wed 11 NovGouda 08:07+1 min—
Tue 10 NovGouda 08:09+2 min+3 min
Mon 9 NovGouda 08:040 min—
Sat 7 NovAmersfoort Centraal 07:34+1 min+2 min
Fri 6 NovGouda 08:04No data—
Thu 5 NovGouda 08:090 min—
Wed 4 NovGouda 08:040 min—
Tue 3 NovGouda 08:290 min—
Mon 2 NovGouda 08:040 min—
Sat 31 OctAmersfoort Centraal 07:30+2 min+3 min
Fri 30 OctGouda 08:060 min—
Thu 29 OctGouda 08:110 min—
Wed 28 OctGouda 08:070 min—
Tue 27 OctGouda 08:080 min—
Mon 26 OctGouda 08:07+1 min—
Sat 24 OctGouda 08:11+3 min+3 min
Fri 23 OctGouda 08:060 min—
Thu 22 OctGouda 08:10No data—
Wed 21 OctGouda 08:060 min—
Tue 20 OctGouda 08:080 min—
Mon 19 OctAmersfoort Centraal 07:27+2 min+2 min