Train NS 1755 Den Haag Centraal – Enschede

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

✓ Today’s run finished

Today, last fix heading to Hengelo at 17:19 0 min

  1. Den Haag Centraal14:55
  2. Gouda15:13
  3. Amersfoort Centraal15:50
  4. Apeldoorn16:16
  5. Deventer16:27
  6. Hengelo17:06
  7. Enschede17:14

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

Next departure 14:55 tomorrow · Den Haag Centraal
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 17 full · 5 partial · 8 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 19 full · 6 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Thu 8 Oct Max en route +6 min · last fix heading to Hengelo +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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