Train NS 6763 Bodegraven – Tiel

Bodegraven 17:16 → Tiel 18:12 Fri, Sat, Sun 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 1 November +2 min

Next service: tomorrow 17:16 from Bodegraven · Fri 6 Nov

Next departure 17:16 tomorrow · Bodegraven
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%
8/8 runs under 3 min
RT coverage: 6 full · 2 partial · 31 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 Tiel, 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

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

  • Early 0% · 0
  • On time 100% · 8
  • 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=1
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 8 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
17:16on time on time
17:23≈ on time ≈ on time
17:33 / 17:35≈ on time ≈ on time
17:37≈ on time ≈ on time
17:40≈ on time ≈ on time
17:43 / 17:44≈ on time ≈ on time
17:47≈ on time ≈ on time
17:53≈ on time ≈ on time
18:00 / 18:01≈ on time ≈ on time
18:08≈ on time ≈ +1 min
18:12on 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 1 NovTiel Passewaaij 18:24Partial coverage+2 min+2 min
Sat 31 OctTiel Passewaaij 18:22Partial coverage0 min—
Fri 30 OctTiel Passewaaij 18:23No data—
Sun 25 OctTiel Passewaaij 18:23No data—
Sat 24 OctZaltbommel 18:350 min—
Fri 23 OctZaltbommel 18:32No data—
Sun 18 OctTiel Passewaaij 18:23+1 min—
Sat 17 OctTiel Passewaaij 18:23No data—
Fri 16 OctTiel Passewaaij 18:27No data—
Sun 11 OctTiel Passewaaij 18:220 min—
Sat 10 OctTiel Passewaaij 18:230 min—
Fri 9 OctTiel Passewaaij 18:220 min—
Mon 5 OctTiel Passewaaij 18:220 min—
Sun 4 OctTiel Passewaaij 18:23No data—
Sat 3 OctTiel Passewaaij 18:23No data—
Fri 2 OctTiel Passewaaij 18:22No data—
Sun 27 SeptTiel Passewaaij 18:26No data—
Sat 26 SeptTiel Passewaaij 18:24No data—
Fri 25 SeptTiel Passewaaij 18:22No data—
Sun 20 SeptTiel Passewaaij 18:22No data—
Sat 19 SeptTiel Passewaaij 18:23No data—
Fri 18 SeptTiel Passewaaij 18:22No data—
Sun 13 SeptTiel Passewaaij 18:24No data—
Sat 12 SeptWoerden 17:38No data—
Fri 11 SeptGeldermalsen 18:15No data—
Sun 6 SeptTiel Passewaaij 18:23No data—
Sat 5 SeptTiel Passewaaij 18:24No data—
Fri 4 SeptTiel Passewaaij 18:22No data—
Sun 30 AugTiel Passewaaij 18:23No data—
Sat 29 AugTiel Passewaaij 18:23No data—