Train NS 6946 Tiel – Den Haag Centraal

Tiel 13:23 → Den Haag Centraal 15:17 Mon, Tue, Wed, Thu, Sat, Sun 1 h 54 min · 21 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Voorburg at 15:27 0 min

  1. Tiel13:23
  2. Culemborg13:50
  3. Utrecht Vaartsche Rijn14:06
  4. Utrecht Terwijde14:20
  5. Gouda Goverwelle14:41
  6. Voorburg15:13
  7. Den Haag Centraal15:17

Next service: tomorrow 13:23 from Tiel · Tue 10 Nov

Next departure 13:23 tomorrow · Tiel
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 5 full · 8 partial · 6 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 5 full · 11 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 4 Nov Max en route +10 min · last fix heading to Voorburg +10 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 75% W n=4
  • 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, 16 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:23on time on time
13:27≈ on time ≈ on time
13:34 / 13:44≈ on time ≈ on time
13:50≈ on time ≈ on time
13:56≈ on time ≈ on time
13:59≈ on time ≈ on time
14:03≈ on time ≈ on time
14:06≈ on time ≈ on time
14:09 / 14:14≈ on time ≈ on time
14:18≈ on time ≈ on time
14:20≈ on time ≈ on time
14:24≈ on time ≈ on time
14:30 / 14:31≈ on time ≈ on time
14:41≈ on time ≈ on time
14:45 / 14:50≈ on time ≈ on time
14:59≈ on time ≈ on time
15:02≈ on time ≈ on time
15:05≈ on time ≈ on time
15:10≈ on time ≈ on time
15:13≈ on time ≈ on time
15:17on 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
Mon 9 NovVoorburg 15:27Partial coverage0 min—
Sun 8 NovVoorburg 15:270 min—
Sat 7 NovVoorburg 15:280 min—
Thu 5 NovVoorburg 15:28No data—
Wed 4 NovVoorburg 15:38Partial coverage+10 min+10 min
Tue 3 NovVoorburg 15:28No data—
Mon 2 NovVoorburg 15:28No data—
Thu 29 OctVoorburg 15:27Partial coverage0 min—
Wed 28 OctVoorburg 15:29Partial coverage0 min—
Tue 27 OctVoorburg 15:28Partial coverage0 min—
Mon 26 OctVoorburg 15:28No data—
Thu 22 OctVoorburg 15:300 min—
Wed 21 OctVoorburg 15:30No data—
Tue 20 OctVoorburg 15:300 min—
Mon 19 OctUtrecht Vaartsche Rijn 14:250 min—
Thu 15 OctVoorburg 15:28Partial coverage0 min—
Wed 14 OctVoorburg 15:28Partial coverage0 min—
Tue 13 OctVoorburg 15:28No data—
Mon 12 OctVoorburg 15:30Partial coverage0 min—
Thu 8 OctVoorburg 15:27Partial coverage0 min—
Wed 7 OctVoorburg 15:28Partial coverage0 min—
Tue 6 OctVoorburg 15:28Partial coverage0 min—
Thu 1 OctVoorburg 15:28No data—
Wed 30 SeptVoorburg 15:30No data—
Tue 29 SeptVoorburg 15:28No data—
Mon 28 SeptVoorburg 15:28No data—
Thu 24 SeptVoorburg 15:28No data—
Wed 23 SeptVoorburg 15:27No data—
Tue 22 SeptVoorburg 15:30No data—
Mon 21 SeptVoorburg 15:28No data—