Train NS 1739 Den Haag Centraal – Enschede

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 10:55 from Den Haag Centraal · Fri 6 Nov

Next departure 10:55 today · Den Haag Centraal
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 18 full · 7 partial · 4 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 19 full · 9 partial · 60 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: +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

  • Sat 24 Oct Max en route +4 min · last fix heading to Deventer +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Hengelo +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Hengelo +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=3
  • 75% F n=4
  • 75% 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, 28 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
10:55on time on time
11:13 / 11:14≈ on time ≈ on time
11:32 / 11:37≈ on time ≈ +1 min
11:50 / 11:52≈ on time ≈ +1 min
12:16 / 12:17≈ on time ≈ +2 min
12:27 / 12:29≈ on time ≈ +2 min
12:54 / 12:55≈ on time ≈ +3 min
13:06 / 13:07≈ on time ≈ +3 min
13:14on time +4 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
Thu 5 NovHengelo 13:19Partial coverage0 min—
Wed 4 NovHengelo 13:22Partial coverage0 min—
Tue 3 NovHengelo 13:23No data—
Mon 2 NovHengelo 13:19Partial coverage0 min—
Sun 1 NovHengelo 13:22+1 min+1 min
Sat 31 OctHengelo 13:220 min—
Fri 30 OctHengelo 13:210 min—
Thu 29 OctHengelo 13:21No data—
Wed 28 OctHengelo 13:21Partial coverage0 min—
Tue 27 OctHengelo 13:22Partial coverage0 min—
Mon 26 OctHengelo 13:21Partial coverage0 min—
Sun 25 OctDeventer 12:57No data—
Sat 24 OctDeventer 13:03+4 min+4 min
Fri 23 OctHengelo 13:210 min—
Thu 22 OctGouda 11:380 min—
Wed 21 OctGouda 11:380 min—
Tue 20 OctGouda 11:330 min—
Mon 19 OctHengelo 13:210 min—
Sun 18 OctUtrecht Centraal 11:510 min—
Sat 17 OctUtrecht Centraal 11:500 min—
Fri 16 OctUtrecht Centraal 11:510 min—
Thu 15 OctUtrecht Centraal 11:55No data—
Wed 14 OctUtrecht Centraal 11:530 min—
Tue 13 OctUtrecht Centraal 11:530 min—
Mon 12 OctUtrecht Centraal 11:520 min—
Sun 11 OctHengelo 13:210 min—
Sat 10 OctHengelo 13:210 min+3 min
Fri 9 OctHengelo 13:24+4 min+4 min
Thu 8 OctHengelo 13:21Partial coverage0 min—
Wed 7 OctHengelo 13:21Partial coverage0 min+1 min