Train NS 1729 Den Haag Centraal – Enschede

Den Haag Centraal 08:25 → Enschede 10:44 Daily 2 h 19 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 08:25 from Den Haag Centraal · Sat 7 Nov

Next departure 08:25 today · Den Haag Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 14 full · 5 partial · 10 no data
On-time · 90 days
85%
47/55 runs under 3 min
RT coverage: 48 full · 7 partial · 31 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: +1 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 29 Sept Max en route +23 min · last fix heading to Amersfoort Centraal +23 min
  • Tue 8 Sept Max en route +16 min · last fix heading to Amersfoort Centraal +16 min
  • Thu 24 Sept Max en route +15 min · last fix heading to Amersfoort Centraal +15 min
  • Thu 8 Oct Max en route +13 min · last fix heading to Hengelo +13 min
  • Mon 7 Sept Max en route +9 min · last fix heading to Amersfoort Centraal +9 min

Distribution · 90 days

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

  • Early 25% · 14
  • On time 60% · 33
  • 3–10 min 7% · 4
  • 10–30 min 7% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 73% T n=11
  • 91% W n=11
  • 75% T n=8
  • 88% F n=8
  • 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, 55 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:25on time on time
08:43 / 08:44≈ on time ≈ +1 min
09:02 / 09:07≈ on time ≈ +2 min
09:20 / 09:22≈ on time ≈ +3 min
09:46 / 09:47≈ on time ≈ +3 min
09:57 / 09:59≈ on time ≈ +3 min
10:24 / 10:25≈ on time ≈ +4 min
10:36 / 10:37≈ on time ≈ +5 min
10:44on time +5 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 6 NovHengelo 10:49No data—
Thu 5 NovHengelo 10:49Partial coverage0 min—
Wed 4 NovHengelo 10:52+1 min—
Tue 3 NovHengelo 10:49Partial coverage0 min—
Mon 2 NovHengelo 10:52No data—
Sun 1 NovHengelo 11:130 min—
Sat 31 OctHengelo 10:510 min—
Fri 30 OctHengelo 10:510 min—
Thu 29 OctHengelo 10:51No data—
Wed 28 OctHengelo 10:52Partial coverage0 min—
Tue 27 OctHengelo 10:51Partial coverage0 min—
Mon 26 OctHengelo 10:53Partial coverage0 min—
Sun 25 OctDeventer 10:24No data—
Sat 24 OctDeventer 10:250 min+1 min
Fri 23 OctHengelo 10:51No data—
Thu 22 OctGouda 09:06No data—
Wed 21 OctGouda 09:030 min—
Tue 20 OctGouda 09:070 min—
Mon 19 OctHengelo 10:510 min—
Sun 18 OctUtrecht Centraal 09:200 min—
Sat 17 OctUtrecht Centraal 09:200 min—
Fri 16 OctUtrecht Centraal 09:210 min—
Thu 15 OctUtrecht Centraal 09:25No data—
Wed 14 OctUtrecht Centraal 09:22No data—
Tue 13 OctUtrecht Centraal 09:35No data—
Mon 12 OctUtrecht Centraal 09:22No data—
Sun 11 OctHengelo 10:510 min—
Sat 10 OctHengelo 10:52+2 min+4 min
Fri 9 OctHengelo 10:52+3 min+3 min
Thu 8 OctHengelo 11:12Partial coverage+13 min+13 min