Train NS 1776 Enschede – Utrecht Centraal

Enschede 20:15 → Utrecht Centraal 21:53 Daily 1 h 38 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 20:15 from Enschede · Thu 5 Nov

Next departure 20:15 today · Enschede
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 5 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sun 18 Oct Max en route +14 min · last fix heading to Amersfoort Centraal +14 min
  • Sun 1 Nov Max en route +7 min · last fix heading to Amersfoort Centraal +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=2
  • 100% F n=3
  • 100% S n=4
  • 33% S n=3

Stops and timetable

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

Last 90 days, 24 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
20:15on time on time
20:22 / 20:23≈ on time ≈ on time
20:34 / 20:35≈ on time ≈ on time
21:00 / 21:03≈ on time ≈ +1 min
21:13 / 21:14≈ on time ≈ +1 min
21:38 / 21:40≈ on time ≈ +2 min
21:53on time +2 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
Wed 4 Nov— 21:590 min—
Tue 3 Nov— 22:420 min—
Mon 2 Nov— 21:59+2 min+2 min
Sun 1 NovAmersfoort Centraal 21:59+7 min+7 min
Sat 31 OctAmersfoort Centraal 22:000 min—
Thu 29 Oct— 21:54+1 min+7 min
Wed 28 Oct— 22:410 min—
Tue 27 Oct— 22:010 min—
Mon 26 Oct— 22:410 min—
Sun 25 OctGouda 22:41No data—
Sat 24 OctGouda 22:360 min—
Fri 23 Oct— 22:40+2 min+2 min
Thu 22 Oct— 22:37No data—
Wed 21 Oct— 22:36No data—
Tue 20 Oct— 22:36No data—
Mon 19 Oct— 21:540 min—
Sun 18 OctAmersfoort Centraal 22:23+14 min+14 min
Sat 17 OctAmersfoort Centraal 22:030 min—
Fri 16 Oct— 22:170 min—
Thu 15 Oct— 22:43No data—
Wed 14 Oct— 22:000 min—
Tue 13 Oct— 21:550 min—
Sun 11 OctAmersfoort Centraal 21:540 min—
Sat 10 OctAmersfoort Centraal 22:42+1 min+1 min
Fri 9 Oct— 21:540 min—
Thu 8 Oct— 22:420 min+4 min
Wed 7 Oct— 22:46+1 min+3 min
Tue 6 Oct— 21:53+1 min+1 min
Mon 5 Oct— 21:54+1 min+1 min
Sun 4 OctAmersfoort Centraal 21:57No data—