Train NS 1751 Den Haag Centraal – Enschede

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

✓ Today’s run finished

Today, last fix heading to Hengelo at 16:19 No data

  1. Den Haag Centraal13:55
  2. Gouda14:13
  3. Amersfoort Centraal14:50
  4. Apeldoorn15:16
  5. Deventer15:27
  6. Hengelo16:06
  7. Enschede16:14

Next service: tomorrow 13:55 from Den Haag Centraal · Sat 7 Nov

Next departure 13:55 tomorrow · Den Haag Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 15 full · 5 partial · 10 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 16 full · 7 partial · 66 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: 0 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 4 Nov Max en route +21 min · last fix heading to Hengelo +21 min
  • Mon 5 Oct Max en route +15 min · last fix heading to Hengelo +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 0% · 0
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

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