Train NS 1731 Utrecht Centraal → Enschede

Utrecht Centraal 09:37 → Enschede 11:17 Daily 1 h 40 min · 8 stops NS (Nederlandse Spoorwegen)

NS 1731 Utrecht Centraal–Enschede: final delay under 3 min on 23 of its 25 runs with data in the last 30 days (92%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 18:49 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Enschede Kennispark at 11:29 0 min

  1. Utrecht Centraal09:37
  2. Amersfoort Centraal09:50
  3. Apeldoorn10:16
  4. Almelo10:54
  5. Hengelo11:06
  6. Enschede Kennispark11:12
  7. Enschede11:17

Next service: tomorrow 09:37 from Utrecht Centraal · Mon 23 Nov

Next departure 09:37 tomorrow · Utrecht Centraal
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 24 full · 1 partial · 5 no data
On-time · 90 days
92%
35/38 runs under 3 min
RT coverage: 37 full · 1 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 10 Nov Max en route +8 min · last fix heading to Hengelo +7 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Apeldoorn +5 min
  • Thu 19 Nov Max en route +3 min · last fix heading to Hengelo +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 35
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 83% W n=6
  • 80% T n=5
  • 100% F n=5
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 38 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
09:37on time on time
09:50 / 09:52≈ on time ≈ on time
10:16 / 10:17≈ on time ≈ +1 min
10:27 / 10:29≈ on time ≈ +1 min
10:54 / 10:55≈ on time ≈ +1 min
11:06 / 11:07≈ on time ≈ +2 min
11:12≈ on time ≈ +2 min
11:17on time +2 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 22 NovEnschede Kennispark 11:29Partial coverage0 min—
Sat 21 NovHengelo 11:220 min+5 min
Fri 20 NovHengelo 11:190 min—
Thu 19 NovHengelo 11:19+3 min+3 min
Wed 18 NovHengelo 11:20+1 min+1 min
Tue 17 NovHengelo 11:190 min—
Mon 16 NovHengelo 11:190 min+6 min
Sun 15 NovHengelo 11:190 min—
Sat 14 NovHengelo 11:190 min—
Fri 13 NovHengelo 11:190 min+1 min
Thu 12 NovHengelo 11:200 min—
Wed 11 NovHengelo 11:190 min—
Tue 10 NovHengelo 11:29+7 min+8 min
Mon 9 NovHengelo 11:190 min—
Sun 8 NovHengelo 11:190 min—
Sat 7 NovHengelo 11:22+2 min+2 min
Fri 6 NovHengelo 11:22No data—
Thu 5 NovHengelo 11:19No data—
Wed 4 NovHengelo 11:190 min—
Tue 3 NovHengelo 11:190 min—
Mon 2 NovHengelo 11:480 min—
Sun 1 NovHengelo 11:24+2 min+2 min
Sat 31 OctHengelo 11:210 min—
Fri 30 OctHengelo 11:210 min—
Thu 29 OctHengelo 11:210 min—
Wed 28 OctHengelo 11:210 min—
Tue 27 OctHengelo 11:21No data—
Mon 26 OctHengelo 11:21No data—
Sun 25 OctDeventer 10:59No data—
Sat 24 OctDeventer 10:57+2 min+2 min