Train NS 1782 Enschede – Utrecht Centraal

Enschede 21:45 → Utrecht Centraal 23:23 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 21:45 from Enschede · Thu 5 Nov

Next departure 21:45 today · Enschede
On-time · 30 days
83%
20/24 runs under 3 min
RT coverage: 24 full · 0 partial · 3 no data
On-time · 90 days
85%
22/26 runs under 3 min
RT coverage: 26 full · 0 partial · 19 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: +5 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 +16 min · last fix heading to Amersfoort Centraal +15 min
  • Wed 7 Oct Max en route +8 min · last fix heading to — +8 min
  • Thu 8 Oct Max en route +7 min · last fix heading to — +6 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Amersfoort Centraal +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 80% W n=5
  • 67% T n=3
  • 100% F n=4
  • 100% S n=3
  • 50% S n=4

Stops and timetable

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

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