Train NS 1779 Utrecht Centraal – Enschede

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

It has not run yet today

Last recorded run: Sunday 8 November +4 min

Next service: today 21:37 from Utrecht Centraal · Sat 14 Nov

Next departure 21:37 today · Utrecht Centraal
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 9 full · 1 partial · 6 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 13 full · 1 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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 8 Nov Max en route +4 min · last fix heading to Hengelo +4 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Hengelo +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • 100% W n=2
  • 100% T n=2
  • 100% F n=1
  • 100% S n=4
  • 50% S n=4

Stops and timetable

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

Last 90 days, 14 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:37on time on time
21:50 / 21:52≈ on time ≈ on time
22:16 / 22:17≈ on time ≈ +1 min
22:27 / 22:29≈ on time ≈ +1 min
22:54 / 22:55≈ on time ≈ +2 min
23:06 / 23:07≈ on time ≈ +2 min
23:14on time +3 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 8 NovHengelo 23:24Partial coverage+4 min+4 min
Sat 7 NovHengelo 23:190 min—
Thu 5 Nov— 23:180 min—
Wed 4 Nov— 23:140 min—
Sun 1 NovHengelo 23:24+4 min+4 min
Sat 31 OctHengelo 23:21No data—
Tue 27 Oct— 23:16No data—
Mon 26 Oct— 23:15No data—
Sun 25 OctDeventer 22:59No data—
Sat 24 OctDeventer 22:550 min—
Fri 23 Oct— 23:160 min—
Thu 22 Oct— 23:16No data—
Tue 20 Oct— 23:22No data—
Mon 19 Oct— 23:200 min—
Sun 18 OctUtrecht Centraal 21:50+3 min+3 min
Sat 17 OctUtrecht Centraal 21:500 min—
Wed 14 Oct— 22:07No data—
Tue 13 Oct— 22:03No data—
Sun 11 OctHengelo 23:23+1 min+1 min
Sat 10 OctAmersfoort Centraal 22:060 min—
Thu 8 Oct— 23:15+1 min+5 min
Wed 7 Oct— 23:150 min—
Tue 6 Oct— 23:20No data—
Sun 4 OctHengelo 23:21No data—
Sat 3 OctHengelo 23:15No data—
Sun 27 SeptHengelo 23:21No data—
Sat 26 SeptHengelo 23:21No data—
Sun 20 SeptHengelo 23:21No data—
Sat 19 SeptAlmelo 23:08No data—
Sun 6 SeptHengelo 23:21No data—