Train NS 6783 Bodegraven – Tiel

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

It has not run yet today

Last recorded run: Wednesday 4 November +7 min

Next service: today 22:16 from Bodegraven · Thu 5 Nov

Next departure 22:16 today · Bodegraven
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 13 full · 1 partial · 14 no data
On-time · 90 days
75%
12/16 runs under 3 min
RT coverage: 15 full · 1 partial · 32 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Thu 29 Oct Max en route +7 min · last fix heading to — +7 min
  • Wed 4 Nov Max en route +7 min · last fix heading to — +7 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 12
  • 3–10 min 25% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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