Train NS 6948 Tiel – Den Haag Centraal

Tiel 13:53 → Den Haag Centraal 15: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 15:59 0 min

  1. Tiel13:53
  2. Culemborg14:20
  3. Utrecht Vaartsche Rijn14:36
  4. Utrecht Terwijde14:50
  5. Gouda Goverwelle15:11
  6. Voorburg15:43
  7. Den Haag Centraal15:47

Next service: Saturday 13:53 from Tiel · Sat 7 Nov

Next departure 13:53 Saturday · Tiel
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 2 full · 10 partial · 6 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 2 full · 11 partial · 37 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=2
  • 100% T n=4
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 13 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:53on time on time
13:57— —
14:04 / 14:14— —
14:20— —
14:26— —
14:29— —
14:33— —
14:36— —
14:39 / 14:44— —
14:48— —
14:50— —
14:54— —
15:00 / 15:01— —
15:11— —
15:15 / 15:20— —
15:29— —
15:32— —
15:35— —
15:40— —
15:43— —
15:47— —

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
Thu 5 NovVoorburg 15:59Partial coverage0 min—
Wed 4 NovVoorburg 15:59Partial coverage+1 min+3 min
Tue 3 NovVoorburg 15:58No data—
Mon 2 NovVoorburg 15:58Partial coverage0 min—
Thu 29 OctVoorburg 16:00Partial coverage0 min—
Wed 28 OctVoorburg 16:01No data—
Tue 27 OctVoorburg 16:00Partial coverage0 min—
Mon 26 OctVoorburg 15:58Partial coverage0 min—
Thu 22 OctVoorburg 16:00No data—
Wed 21 OctVoorburg 16:00No data—
Tue 20 OctVoorburg 16:000 min—
Mon 19 OctUtrecht Vaartsche Rijn 14:550 min—
Thu 15 OctVoorburg 15:58Partial coverage0 min—
Wed 14 OctVoorburg 15:59No data—
Tue 13 OctVoorburg 15:59No data—
Mon 12 OctVoorburg 15:57Partial coverage0 min—
Thu 8 OctVoorburg 15:57Partial coverage0 min—
Wed 7 OctVoorburg 15:57Partial coverage0 min—
Tue 6 OctVoorburg 15:57Partial coverage0 min—
Thu 1 OctVoorburg 16:00No data—
Wed 30 SeptVoorburg 15:57No data—
Tue 29 SeptVoorburg 15:58No data—
Mon 28 SeptVoorburg 15:57No data—
Thu 24 SeptVoorburg 15:58No data—
Wed 23 SeptVoorburg 15:57No data—
Tue 22 SeptVoorburg 15:58No data—
Mon 21 SeptVoorburg 15:58No data—
Thu 17 SeptVoorburg 15:59No data—
Wed 16 SeptVoorburg 15:59No data—
Tue 15 SeptVoorburg 15:58No data—