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)

It does not run today

Last recorded run: Saturday 7 November +1 min

Next service: tomorrow 05:45 from Enschede · Mon 9 Nov

Next departure 05:45 tomorrow · Enschede
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 21 full · 2 partial · 2 no data
On-time · 90 days
83%
54/65 runs under 3 min
RT coverage: 63 full · 2 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +2 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

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

  • Early 3% · 2
  • On time 80% · 52
  • 3–10 min 12% · 8
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 80% T n=10
  • 100% W n=11
  • 67% T n=12
  • 58% F n=12
  • 100% S n=8
  • — S n=0

Stops and timetable

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

Last 90 days, 65 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
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 ≈ +4 min
07:23on 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

DateLast stopFinalMax
Sat 7 NovAmersfoort Centraal 07:34Partial coverage+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:27Partial coverage+2 min+2 min
Sat 17 OctAmersfoort Centraal 07:31+2 min+3 min
Fri 16 OctGouda 08:070 min—
Thu 15 OctGouda 08:070 min—
Wed 14 OctGouda 08:110 min—
Tue 13 OctGouda 08:210 min—
Mon 12 OctGouda 08:090 min—
Sat 10 OctAmersfoort Centraal 07:250 min—
Fri 9 OctGouda 08:12+4 min+6 min
Thu 8 OctGouda 08:23+18 min+18 min
Wed 7 OctGouda 08:06+1 min+1 min
Tue 6 OctAmersfoort Centraal 08:39+16 min+16 min
Mon 5 OctGouda 08:19+2 min+13 min