Train NS 6773 Bodegraven – Tiel

Bodegraven 19:46 → Tiel 20:42 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 19:46 from Bodegraven · Mon 9 Nov

Next departure 19:46 Monday · Bodegraven
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 11 full · 3 partial · 15 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 15 full · 3 partial · 38 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

  • Mon 5 Oct Max en route +6 min · last fix heading to — +5 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Tiel Passewaaij +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 15
  • 3–10 min 17% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 75% F n=4
  • 50% 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, 18 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
19:46on time +1 min
19:53≈ on time ≈ +1 min
20:03 / 20:05≈ on time ≈ +2 min
20:07≈ on time ≈ +2 min
20:10≈ on time ≈ +2 min
20:13 / 20:14≈ on time ≈ +2 min
20:17≈ on time ≈ +2 min
20:23≈ +1 min ≈ +2 min
20:30 / 20:31≈ +1 min ≈ +2 min
20:38≈ +1 min ≈ +2 min
20: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 Nov— 20:44+1 min—
Thu 5 Nov— 20:45No data—
Wed 4 Nov— 20:44+1 min—
Tue 3 Nov— 20:45No data—
Mon 2 Nov— 20:48No data—
Sun 1 NovTiel Passewaaij 20:54Partial coverage+2 min+2 min
Sat 31 OctTiel Passewaaij 20:58Partial coverage+3 min+3 min
Fri 30 Oct— 20:43No data—
Thu 29 Oct— 20:45+2 min+2 min
Wed 28 Oct— 20:45No data—
Tue 27 Oct— 20:500 min—
Mon 26 OctBodegraven 20:45No data—
Sun 25 OctTiel Passewaaij 20:53No data—
Sat 24 OctZaltbommel 21:02No data—
Fri 23 Oct— 21:01+3 min+3 min
Thu 22 Oct— 20:46No data—
Wed 21 Oct— 20:46No data—
Tue 20 Oct— 20:50No data—
Mon 19 Oct— 20:460 min—
Sun 18 OctTiel Passewaaij 20:53+1 min—
Sat 17 OctTiel Passewaaij 20:53No data—
Fri 16 OctWoerden 20:45Partial coverage+1 min—
Thu 15 Oct— 20:44No data—
Wed 14 OctBodegraven 20:43No data—
Tue 13 Oct— 20:45No data—
Mon 12 Oct— 20:450 min—
Sun 11 OctTiel Passewaaij 20:53+1 min—
Sat 10 OctTiel Passewaaij 20:53+1 min+1 min
Fri 9 Oct— 20:44+1 min+2 min
Thu 8 Oct— 20:460 min—