Train NS 1774 Enschede – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 19 November +2 min

Next service: today 19:45 from Enschede · Fri 20 Nov

Next departure 19:45 today · Enschede
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 4 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 34 full · 0 partial · 17 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

  • Wed 7 Oct Max en route +17 min · last fix heading to — +16 min
  • Fri 13 Nov Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 86% W n=7
  • 100% T n=5
  • 80% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 34 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
19:45on time on time
19:52 / 19:53≈ on time ≈ on time
20:04 / 20:05≈ on time ≈ on time
20:30 / 20:33≈ on time ≈ +1 min
20:43 / 20:44≈ on time ≈ +1 min
21:08 / 21:10≈ on time ≈ +2 min
21:23on 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
Thu 19 Nov— 21:24+2 min+2 min
Wed 18 Nov— 21:240 min+1 min
Tue 17 Nov— 21:240 min—
Mon 16 Nov— 21:24+1 min—
Sun 15 NovAmersfoort Centraal 21:290 min+3 min
Sat 14 NovAmersfoort Centraal 21:24+1 min+1 min
Fri 13 Nov— 22:14+3 min+5 min
Thu 12 Nov— 22:14+1 min+3 min
Wed 11 Nov— 21:240 min—
Sun 8 NovAmersfoort Centraal 21:240 min—
Sat 7 NovAmersfoort Centraal 21:240 min—
Fri 6 Nov— 21:24+2 min+3 min
Thu 5 Nov— 22:090 min—
Wed 4 Nov— 21:24+1 min+2 min
Sun 1 NovAmersfoort Centraal 21:290 min—
Sat 31 OctAmersfoort Centraal 22:150 min—
Fri 30 Oct— 22:17No data—
Thu 29 Oct— 22:110 min—
Wed 28 Oct— 22:140 min—
Tue 27 Oct— 22:180 min—
Mon 26 OctAlmelo 21:240 min—
Sun 25 OctGouda 22:06No data—
Sat 24 OctUtrecht Centraal 22:22No data—
Fri 23 Oct— 22:060 min—
Thu 22 Oct— 22:08No data—
Wed 21 Oct— 22:060 min—
Mon 19 Oct— 21:270 min—
Sun 18 OctAmersfoort Centraal 21:27+1 min—
Sat 17 OctAmersfoort Centraal 21:25No data—
Fri 16 Oct— 22:12+1 min+2 min