Train NS 1785 Utrecht Centraal – Enschede

Utrecht Centraal 23:07 → Enschede 00:44 Daily 1 h 37 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 23:07 from Utrecht Centraal · Fri 6 Nov

Next departure 23:07 today · Utrecht Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 14 full · 2 partial · 3 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 14 full · 2 partial · 16 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

  • Sun 18 Oct Max en route +9 min · last fix heading to Utrecht Centraal +9 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
23:07on time on time
23:20 / 23:22≈ on time ≈ on time
23:46 / 23:47≈ on time ≈ on time
23:57 / 23:59≈ on time ≈ +1 min
00:24 / 00:25≈ on time ≈ +1 min
00:36 / 00:37≈ on time ≈ +1 min
00:44on time +1 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
Sun 1 NovHengelo 00:49Partial coverage0 min+2 min
Sat 31 OctUtrecht Centraal 00:45Partial coverage0 min—
Thu 29 Oct— 00:450 min—
Sun 25 OctDeventer 00:240 min—
Sat 24 OctDen Haag Centraal 00:27No data—
Fri 23 Oct— 00:46+2 min+2 min
Thu 22 Oct— 00:460 min—
Wed 21 Oct— 00:450 min—
Tue 20 Oct— 00:540 min—
Mon 19 Oct— 01:280 min+28 min
Sun 18 OctUtrecht Centraal 23:39+9 min+9 min
Sat 17 OctUtrecht Centraal 23:200 min—
Fri 16 Oct— 23:20No data—
Wed 14 Oct— 23:200 min—
Tue 13 Oct— 23:20No data—
Sun 11 OctHengelo 00:510 min—
Sat 10 Oct— 00:460 min—
Fri 9 Oct— 00:450 min—
Thu 8 Oct— 00:460 min—
Sun 4 OctHengelo 00:52No data—
Sat 3 OctAlmelo 00:39No data—
Sun 27 SeptHengelo 00:51No data—
Sat 26 SeptAmersfoort Centraal 23:36No data—
Sun 20 SeptHengelo 00:51No data—
Sat 19 SeptDuivendrecht 23:04No data—
Sun 6 SeptHengelo 00:51No data—
Sun 30 AugHengelo 00:51No data—
Sun 23 AugHengelo 00:51No data—
Sat 22 AugApeldoorn 00:01No data—
Sun 16 AugHengelo 00:51No data—