Train NS 1731 Den Haag Centraal – Enschede

Den Haag Centraal 08:55 → Enschede 11:14 Daily 2 h 19 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 08:55 from Den Haag Centraal · Thu 5 Nov

Next departure 08:55 today · Den Haag Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 15 full · 6 partial · 8 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 15 full · 7 partial · 65 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

  • Wed 7 Oct Max en route +5 min · last fix heading to Apeldoorn +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
08:55on time on time
09:13 / 09:14≈ on time ≈ on time
09:32 / 09:37≈ on 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 ≈ +1 min
11:14on 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
Wed 4 NovHengelo 11:19Partial coverage0 min—
Tue 3 NovHengelo 11:19Partial coverage0 min—
Mon 2 NovHengelo 11:48Partial coverage0 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:21Partial coverage0 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
Fri 23 OctHengelo 11:21No data—
Thu 22 OctGouda 09:460 min—
Wed 21 OctGouda 09:340 min—
Tue 20 OctGouda 09:330 min—
Mon 19 OctHengelo 11:210 min—
Sun 18 OctUtrecht Centraal 09:510 min—
Sat 17 OctUtrecht Centraal 09:500 min—
Fri 16 OctUtrecht Centraal 09:510 min—
Thu 15 OctUtrecht Centraal 10:58No data—
Wed 14 OctUtrecht Centraal 09:51No data—
Tue 13 OctUtrecht Centraal 09:52No data—
Mon 12 OctUtrecht Centraal 09:59No data—
Sun 11 OctHengelo 11:210 min—
Sat 10 OctHengelo 11:210 min—
Fri 9 OctHengelo 11:210 min—
Thu 8 OctHengelo 11:21Partial coverage0 min+6 min
Wed 7 OctApeldoorn 12:02Partial coverage+5 min+5 min
Tue 6 OctHengelo 11:21Partial coverage0 min—