Train NS 6768 Tiel – Bodegraven

Tiel 18:48 → Bodegraven 19:45 Fri, Sat, Sun 0 h 57 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Friday 18:48 from Tiel · Fri 13 Nov

Next departure 18:48 Friday · Tiel
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 5 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 7 full · 2 partial · 28 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 Bodegraven, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
18:48on time on time
18:51≈ on time ≈ on time
18:59 / 19:00≈ on time ≈ on time
19:05≈ on time ≈ on time
19:11 / 19:12≈ on time ≈ on time
19:15≈ on time ≈ on time
19:19≈ on time ≈ on time
19:22≈ on time ≈ on time
19:25 / 19:26≈ on time ≈ on time
19:36 / 19:37≈ on time ≈ on time
19:45on 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
Fri 6 Nov— 19:44+1 min—
Sun 1 NovWoerden 19:53Partial coverage+1 min+3 min
Sat 31 OctWoerden 19:51Partial coverage0 min—
Fri 30 OctTiel Passewaaij 19:46No data—
Sun 25 OctWoerden 19:51No data—
Sat 24 OctWoerden 19:51No data—
Fri 23 OctUtrecht Centraal 19:450 min—
Sun 18 OctUtrecht Vaartsche Rijn 19:360 min—
Sat 17 OctWoerden 19:51No data—
Fri 16 OctWoerden 19:51No data—
Sun 11 OctLeiden Lammenschans 20:170 min—
Sat 10 OctLeiden Lammenschans 20:170 min—
Fri 9 Oct— 20:080 min+1 min
Mon 5 Oct— 20:080 min—
Sun 4 OctLeiden Lammenschans 20:17No data—
Sat 3 OctLeiden Lammenschans 20:19No data—
Fri 2 OctTiel 19:02No data—
Sun 27 SeptLeiden Lammenschans 20:17No data—
Sat 26 SeptLeiden Lammenschans 20:17No data—
Sun 20 SeptLeiden Lammenschans 20:17No data—
Sat 19 SeptLeiden Lammenschans 20:18No data—
Fri 18 SeptTiel 19:02No data—
Sun 13 SeptLeiden Lammenschans 20:19No data—
Sat 12 SeptLeiden Lammenschans 20:17No data—
Fri 11 SeptTiel Passewaaij 18:55No data—
Sun 6 SeptLeiden Lammenschans 20:30No data—
Sat 5 SeptLeiden Lammenschans 20:17No data—
Fri 4 SeptTiel Passewaaij 19:05No data—
Sun 30 AugLeiden Lammenschans 20:18No data—
Sat 29 AugLeiden Lammenschans 20:18No data—