Train NS 1783 Utrecht Centraal – Enschede

Utrecht Centraal 22:37 → Enschede 00:14 Daily 1 h 37 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 22:37 from Utrecht Centraal · Thu 19 Nov

Next departure 22:37 today · Utrecht Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 11 full · 6 partial · 1 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 20 full · 6 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Enschede, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 14 Nov Max en route +13 min · last fix heading to Amersfoort Centraal +11 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 96% · 25
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=2
  • 100% T n=4
  • 100% F n=2
  • 75% S n=4
  • 100% S n=6

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
22:37on time on time
22:50 / 22:52≈ on time ≈ on time
23:16 / 23:17≈ on time ≈ on time
23:27 / 23:29≈ on time ≈ on time
23:54 / 23:56≈ on time ≈ +1 min
00:06 / 00:07≈ on time ≈ on time
00:14on time on time

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
Tue 17 Nov— 00:14+1 min+3 min
Mon 16 NovDeventer 00:14Partial coverage0 min—
Sun 15 NovHengelo 00:19Partial coverage0 min—
Sat 14 NovAmersfoort Centraal 00:14Partial coverage+11 min+13 min
Mon 9 Nov— 00:140 min+5 min
Sun 8 NovHengelo 00:22Partial coverage0 min—
Sat 7 NovApeldoorn 00:19+2 min+4 min
Thu 5 Nov— 00:190 min—
Sun 1 NovHengelo 00:22Partial coverage0 min—
Sat 31 OctApeldoorn 23:31No data—
Thu 29 Oct— 00:150 min—
Tue 27 Oct— 00:160 min—
Mon 26 Oct— 00:160 min—
Sun 25 OctDeventer 00:04Partial coverage0 min—
Sat 24 OctUtrecht Centraal 00:020 min—
Fri 23 Oct— 00:160 min—
Thu 22 Oct— 00:440 min—
Wed 21 Oct— 00:150 min—
Tue 20 Oct— 00:200 min—
Mon 19 Oct— 00:160 min+3 min
Sun 18 OctUtrecht Centraal 22:500 min—
Sat 17 OctUtrecht Centraal 22:500 min—
Wed 14 Oct— 22:500 min—
Sun 11 OctHengelo 00:220 min+5 min
Fri 9 Oct— 00:150 min—
Thu 8 Oct— 00:170 min—
Tue 6 Oct— 00:150 min—
Sun 4 OctHengelo 00:22No data—
Sat 3 OctHengelo 00:18No data—
Sun 27 SeptHengelo 00:25No data—