Train NS 1787 Utrecht Centraal – Enschede

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 23:37 from Utrecht Centraal · Thu 5 Nov

Next departure 23:37 today · Utrecht Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Mon 5 Oct Max en route +38 min · last fix heading to — +38 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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:37on time on time
23:50 / 23:52≈ on time ≈ +2 min
00:16 / 00:17≈ on time ≈ +2 min
00:27 / 00:29≈ on time ≈ +1 min
00:54 / 00:55≈ on time ≈ +1 min
01:06 / 01:07≈ on time ≈ on time
01: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
Wed 4 Nov— 00:540 min—
Sun 1 NovHengelo 01:190 min—
Thu 29 Oct— 01:150 min+3 min
Wed 28 Oct— 01:170 min—
Tue 27 Oct— 01:160 min—
Mon 26 OctApeldoorn 01:220 min—
Sun 25 OctApeldoorn 00:310 min—
Sat 24 Oct— 00:590 min—
Fri 23 Oct— 01:160 min—
Thu 22 Oct— 01:260 min—
Wed 21 Oct— 01:150 min—
Tue 20 Oct— 01:150 min—
Mon 19 Oct— 01:160 min+7 min
Sun 18 OctUtrecht Centraal 00:060 min+8 min
Sat 17 OctUtrecht Centraal 23:500 min—
Sun 11 OctHengelo 01:210 min—
Fri 9 Oct— 01:150 min—
Thu 8 Oct— 01:150 min—
Wed 7 Oct— 01:210 min+3 min
Tue 6 Oct— 01:170 min—
Mon 5 Oct— 23:52+38 min+38 min
Sun 4 OctHengelo 01:22No data—
Sat 3 OctDeventer 00:43No data—
Sun 27 SeptHengelo 01:22No data—
Sat 26 SeptUtrecht Centraal 23:51No data—
Sun 20 SeptHengelo 01:21No data—
Sun 6 SeptHengelo 01:21No data—
Sun 30 AugHengelo 01:21No data—
Sun 23 AugHengelo 01:21No data—
Sat 22 AugAmersfoort Centraal 00:06No data—