Train NS 6779 Bodegraven – Tiel

Bodegraven 21:16 → Tiel 22:12 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +2 min

Next service: Monday 21:16 from Bodegraven · Mon 9 Nov

Next departure 21:16 Monday · Bodegraven
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 13 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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 11 Oct Max en route +6 min · last fix heading to Tiel Passewaaij +5 min
  • Tue 6 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 50% T n=2
  • 100% W n=2
  • 100% T n=3
  • 100% F n=4
  • 100% S n=1
  • 67% S n=3

Stops and timetable

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

Last 90 days, 19 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
21:16on time on time
21:23≈ on time ≈ on time
21:33 / 21:35≈ on time ≈ +1 min
21:37≈ on time ≈ +1 min
21:40≈ on time ≈ +1 min
21:43 / 21:44≈ on time ≈ +2 min
21:47≈ on time ≈ +2 min
21:53≈ on time ≈ +2 min
22:00 / 22:01≈ on time ≈ +3 min
22:08≈ on time ≈ +3 min
22:12on time +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 Nov— 22:14+2 min+2 min
Thu 5 Nov— 22:19No data—
Wed 4 Nov— 22:140 min—
Tue 3 Nov— 22:13No data—
Mon 2 Nov— 22:13+1 min—
Sun 1 NovTiel Passewaaij 22:23Partial coverage0 min—
Sat 31 OctTiel Passewaaij 22:22No data—
Thu 29 Oct— 22:15+2 min+3 min
Wed 28 Oct— 22:20No data—
Tue 27 Oct— 22:14No data—
Mon 26 Oct— 22:13No data—
Sun 25 OctTiel Passewaaij 22:23No data—
Sat 24 OctZaltbommel 22:32No data—
Fri 23 Oct— 22:290 min—
Thu 22 Oct— 22:15No data—
Wed 21 Oct— 22:15No data—
Tue 20 Oct— 22:150 min—
Mon 19 Oct— 22:130 min—
Sun 18 OctTiel Passewaaij 22:23+1 min—
Sat 17 OctTiel Passewaaij 22:23No data—
Fri 16 Oct— 22:150 min—
Thu 15 Oct— 22:150 min—
Wed 14 Oct— 22:13No data—
Tue 13 Oct— 22:15No data—
Mon 12 Oct— 22:130 min—
Sun 11 OctTiel Passewaaij 22:27+5 min+6 min
Sat 10 OctGeldermalsen 22:16+3 min+3 min
Fri 9 Oct— 22:150 min—
Thu 8 Oct— 22:140 min—
Wed 7 Oct— 22:13+1 min—