Train NS 6757 Bodegraven – Tiel

Bodegraven 15:46 → Tiel 16:42 Fri, Sat, Sun 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Friday 15:46 from Bodegraven · Fri 13 Nov

Next departure 15:46 Friday · Bodegraven
On-time · 30 days
73%
8/11 runs under 3 min
RT coverage: 8 full · 3 partial · 2 no data
On-time · 90 days
75%
9/12 runs under 3 min
RT coverage: 9 full · 3 partial · 24 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Sun 1 Nov Max en route +6 min · last fix heading to Tiel Passewaaij +6 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Tiel Passewaaij +3 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Tiel Passewaaij +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 9
  • 3–10 min 25% · 3
  • 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
  • 75% F n=4
  • 100% S n=4
  • 33% S n=3

Stops and timetable

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

Last 90 days, 12 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
15:46on time on time
15:53≈ on time ≈ on time
16:03 / 16:05≈ on time ≈ +1 min
16:07≈ on time ≈ +1 min
16:10≈ on time ≈ +1 min
16:13 / 16:14≈ on time ≈ +2 min
16:17≈ on time ≈ +2 min
16:23≈ on time ≈ +2 min
16:30 / 16:31≈ +1 min ≈ +3 min
16:38≈ +1 min ≈ +3 min
16:42+1 min +3 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 NovTiel Passewaaij 16:53No data—
Sun 1 NovTiel Passewaaij 16:58Partial coverage+6 min+6 min
Sat 31 OctTiel Passewaaij 16:53Partial coverage+1 min—
Fri 30 OctTiel Passewaaij 16:540 min—
Sun 25 OctTiel Passewaaij 16:56No data—
Sat 24 OctZaltbommel 17:050 min—
Fri 23 OctZaltbommel 17:020 min—
Sun 18 OctTiel Passewaaij 16:56+3 min+4 min
Sat 17 OctTiel Passewaaij 16:53Partial coverage0 min—
Fri 16 OctTiel Passewaaij 16:530 min—
Sun 11 OctTiel Passewaaij 16:53+1 min—
Sat 10 OctTiel Passewaaij 16:54+1 min—
Fri 9 OctTiel Passewaaij 16:56+3 min+4 min
Mon 5 OctTiel Passewaaij 16:54+2 min+2 min
Sun 4 OctTiel Passewaaij 16:55No data—
Sat 3 OctTiel Passewaaij 16:55No data—
Fri 2 OctTiel Passewaaij 16:54No data—
Sun 27 SeptTiel Passewaaij 16:55No data—
Sat 26 SeptTiel Passewaaij 16:54No data—
Fri 25 SeptTiel Passewaaij 16:53No data—
Sun 20 SeptTiel Passewaaij 16:52No data—
Sat 19 SeptTiel Passewaaij 17:04No data—
Fri 18 SeptTiel Passewaaij 16:53No data—
Sun 13 SeptTiel Passewaaij 16:52No data—
Sat 12 SeptWoerden 16:09No data—
Fri 11 SeptTiel Passewaaij 17:06No data—
Sun 6 SeptTiel Passewaaij 16:55No data—
Sat 5 SeptTiel Passewaaij 16:52No data—
Fri 4 SeptTiel Passewaaij 16:53No data—
Sun 30 AugTiel Passewaaij 16:54No data—