Train NS 6960 Tiel – Den Haag Centraal

Tiel 16:53 → Den Haag Centraal 18:47 Mon, Tue, Wed, Thu, Sat, Sun 1 h 54 min · 21 stops NS (Nederlandse Spoorwegen)

Running now · updated 18:20

Heading to Den Haag Centraal 0 min

Estimated arrival at Den Haag Centraal 18:47 · 0 km/h

  1. Tiel16:53
  2. Culemborg17:20
  3. Utrecht Vaartsche Rijn17:36
  4. Utrecht Terwijde17:50
  5. Gouda Goverwelle18:11
  6. Zoetermeer18:35
  7. Den Haag Centraal18:47

Today it is running no worse than usual: typical arrival delay is 0 min; 93% of the last 15 runs arrived on time.

On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 13 full · 2 partial · 3 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 33 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 Den Haag Centraal, 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 28 Oct Max en route +4 min · last fix heading to Gouda Goverwelle +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 67% W n=3
  • 100% T n=4
  • — F n=0
  • 100% S n=1
  • 100% S n=1

Stops and timetable

Timetable of the latest run from the operator’s GTFS (21 stops).

Last 90 days, 18 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 10Today
16:53on time on time
16:57≈ on time ≈ on time
17:04 / 17:14≈ on time ≈ on time
17:20≈ on time ≈ on time
17:26≈ on time ≈ +1 min
17:29≈ on time ≈ +1 min
17:33≈ on time ≈ +1 min
17:36≈ on time ≈ +1 min
17:39 / 17:44≈ on time ≈ +1 min
17:48≈ on time ≈ +1 min
17:50≈ on time ≈ +1 min
17:54≈ on time ≈ +1 min
18:00 / 18:01≈ on time ≈ +1 min
18:11≈ on time ≈ +1 min
18:15 / 18:20≈ on time ≈ +1 min
18:29≈ on time ≈ +1 min
18:33≈ on time ≈ +1 min
18:35≈ on time ≈ +1 min
18:40≈ on time ≈ +1 min
18:43≈ on time ≈ +1 min
18:47on 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
Sun 8 NovGouda 18:19Partial coverage0 min—
Sat 7 NovVoorburg 18:58Partial coverage0 min—
Thu 5 NovGouda Goverwelle 18:480 min—
Wed 4 NovGouda Goverwelle 18:48No data—
Tue 3 NovGouda Goverwelle 18:490 min—
Mon 2 NovWoerden 18:53+2 min+2 min
Thu 29 OctWoerden 18:150 min—
Wed 28 OctGouda Goverwelle 18:55+4 min+4 min
Tue 27 OctWoerden 18:490 min—
Mon 26 OctWoerden 18:500 min—
Thu 22 OctVoorburg 18:590 min—
Wed 21 OctZoetermeer 18:51No data—
Tue 20 OctCulemborg 18:580 min—
Mon 19 OctUtrecht Vaartsche Rijn 17:550 min—
Thu 15 OctLansingerland-Zoetermeer 18:48No data—
Wed 14 OctVoorburg 18:570 min—
Tue 13 OctDen Haag Ypenburg 18:510 min—
Mon 12 OctVoorburg 18:590 min—
Thu 8 OctWoerden 18:490 min—
Wed 7 OctWoerden 18:51+1 min+2 min
Tue 6 OctWoerden 18:510 min+1 min
Thu 1 OctWoerden 18:15No data—
Wed 30 SeptWoerden 18:15No data—
Tue 29 SeptWoerden 18:15No data—
Mon 28 SeptWoerden 18:15No data—
Thu 24 SeptVleuten 18:09No data—
Wed 23 SeptGouda Goverwelle 18:25No data—
Tue 22 SeptWoerden 18:15No data—
Mon 21 SeptWoerden 18:15No data—
Thu 17 SeptGouda Goverwelle 18:25No data—