Train NS 1727 Den Haag Centraal → Enschede

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 07:55 from Den Haag Centraal · Sun 22 Nov

Next departure 07:55 tomorrow · Den Haag Centraal
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 22 full · 2 partial · 5 no data
On-time · 90 days
88%
37/42 runs under 3 min
RT coverage: 40 full · 2 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 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 +16 min · last fix heading to Hengelo +16 min
  • Mon 16 Nov Max en route +12 min · last fix heading to Hengelo +12 min
  • Thu 24 Sept Max en route +9 min · last fix heading to Utrecht Centraal +9 min
  • Thu 12 Nov Max en route +9 min · last fix heading to Hengelo +9 min
  • Wed 7 Oct Max en route +7 min · last fix heading to Hengelo +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 37
  • 3–10 min 7% · 3
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 83% T n=6
  • 83% W n=6
  • 71% T n=7
  • 100% F n=6
  • 100% S n=6
  • 100% S n=4

Stops and timetable

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

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