Train NS 1737 Den Haag Centraal – Enschede

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

✓ Today’s run finished

Today, last fix heading to Hengelo at 12:49 No data

  1. Den Haag Centraal10:25
  2. Gouda10:43
  3. Amersfoort Centraal11:20
  4. Apeldoorn11:46
  5. Deventer11:57
  6. Hengelo12:36
  7. Enschede12:44

Next service: tomorrow 10:25 from Den Haag Centraal · Sat 7 Nov

Next departure 10:25 tomorrow · Den Haag Centraal
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 19 full · 5 partial · 6 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 20 full · 7 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: 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

  • Sun 1 Nov Max en route +3 min · last fix heading to Hengelo +3 min

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 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=2
  • 100% F n=4
  • 100% S n=4
  • 67% 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
10:25on time on time
10:43 / 10:44≈ on time ≈ on time
11:02 / 11:07≈ on time ≈ on time
11:20 / 11:22≈ on time ≈ on time
11:46 / 11:47≈ on time ≈ on time
11:57 / 11:59≈ on time ≈ on time
12:24 / 12:25≈ on time ≈ on time
12:36 / 12:37≈ on time ≈ on time
12:44on time on time

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 12:49No data—
Thu 5 NovHengelo 12:49Partial coverage0 min—
Wed 4 NovHengelo 12:490 min+2 min
Tue 3 NovHengelo 13:39Partial coverage0 min—
Mon 2 NovHengelo 12:49Partial coverage0 min—
Sun 1 NovHengelo 12:52+3 min+3 min
Sat 31 OctHengelo 13:010 min—
Fri 30 OctHengelo 12:510 min—
Thu 29 OctHengelo 12:51No data—
Wed 28 OctHengelo 12:510 min—
Tue 27 OctHengelo 12:51Partial coverage0 min—
Mon 26 OctHengelo 12:510 min—
Sun 25 OctDeventer 12:26No data—
Sat 24 OctDeventer 12:240 min—
Fri 23 OctHengelo 12:530 min—
Thu 22 OctGouda 11:03No data—
Wed 21 OctGouda 11:080 min—
Tue 20 OctGouda 11:040 min—
Mon 19 OctHengelo 12:530 min—
Sun 18 OctUtrecht Centraal 11:200 min—
Sat 17 OctUtrecht Centraal 11:210 min—
Fri 16 OctUtrecht Centraal 11:220 min—
Thu 15 OctUtrecht Centraal 11:21No data—
Wed 14 OctUtrecht Centraal 11:210 min—
Tue 13 OctUtrecht Centraal 11:23No data—
Mon 12 OctUtrecht Centraal 11:210 min—
Sun 11 OctHengelo 12:510 min—
Sat 10 OctHengelo 12:510 min—
Fri 9 OctHengelo 12:510 min—
Thu 8 OctHengelo 12:52Partial coverage+1 min+2 min