Train NS 6928 Tiel – Den Haag Centraal

Tiel 08:53 → Den Haag Centraal 10:47 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 10:58 0 min

  1. Tiel08:53
  2. Culemborg09:20
  3. Utrecht Vaartsche Rijn09:36
  4. Utrecht Terwijde09:50
  5. Gouda Goverwelle10:11
  6. Voorburg10:43
  7. Den Haag Centraal10:47

Next service: tomorrow 08:53 from Tiel · Wed 11 Nov

Next departure 08:53 tomorrow · Tiel
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 6 full · 8 partial · 6 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 7 full · 10 partial · 34 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% 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, 17 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
08:53on time on time
08:57≈ on time ≈ on time
09:04 / 09:14≈ on time ≈ on time
09:20≈ on time ≈ on time
09:26≈ on time ≈ on time
09:29≈ on time ≈ on time
09:33≈ on time ≈ on time
09:36≈ on time ≈ on time
09:39 / 09:44≈ on time ≈ on time
09:48≈ on time ≈ on time
09:50≈ on time ≈ +1 min
09:54≈ on time ≈ +1 min
10:00 / 10:01≈ on time ≈ +1 min
10:11≈ on time ≈ +1 min
10:15 / 10:20≈ on time ≈ +1 min
10:29≈ on time ≈ +1 min
10:32≈ on time ≈ +1 min
10:35≈ on time ≈ +1 min
10:40≈ on time ≈ +1 min
10:43≈ on time ≈ +1 min
10: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
Tue 10 NovVoorburg 10:580 min—
Mon 9 NovVoorburg 10:59Partial coverage+1 min+1 min
Sun 8 NovVoorburg 10:57+2 min+2 min
Sat 7 NovVoorburg 10:580 min—
Thu 5 NovVoorburg 10:58No data—
Wed 4 NovVoorburg 10:58Partial coverage0 min—
Tue 3 NovVoorburg 10:59No data—
Mon 2 NovVoorburg 10:57No data—
Thu 29 OctVoorburg 10:59Partial coverage0 min—
Wed 28 OctVoorburg 10:57Partial coverage0 min—
Tue 27 OctVoorburg 10:58Partial coverage0 min—
Mon 26 OctVoorburg 10:58No data—
Thu 22 OctVoorburg 11:010 min—
Wed 21 OctVoorburg 11:11No data—
Tue 20 OctVoorburg 11:000 min—
Mon 19 OctUtrecht Vaartsche Rijn 09:560 min—
Thu 15 OctVoorburg 10:58Partial coverage0 min—
Wed 14 OctVoorburg 10:58Partial coverage0 min—
Tue 13 OctVoorburg 11:01No data—
Mon 12 OctVoorburg 10:57Partial coverage0 min—
Thu 8 OctVoorburg 10:58Partial coverage0 min—
Wed 7 OctZoetermeer Oost 12:010 min—
Tue 6 OctVoorburg 10:58Partial coverage0 min—
Thu 1 OctVoorburg 10:58No data—
Wed 30 SeptVoorburg 10:58No data—
Tue 29 SeptVoorburg 10:58No data—
Mon 28 SeptVoorburg 10:58No data—
Thu 24 SeptVoorburg 10:58No data—
Wed 23 SeptVoorburg 10:58No data—
Tue 22 SeptVoorburg 10:57No data—