Train NS 1747 Den Haag Centraal – Enschede

Den Haag Centraal 12:55 → Enschede 15:14 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 12:55 from Den Haag Centraal · Sat 7 Nov

Next departure 12:55 today · Den Haag Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 19 full · 4 partial · 6 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 21 full · 6 partial · 61 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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