Train NS 6785 Bodegraven – Tiel

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 22:46 from Bodegraven · Fri 6 Nov

Next departure 22:46 today · Bodegraven
On-time · 30 days
81%
13/16 runs under 3 min
RT coverage: 15 full · 1 partial · 11 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 18 full · 1 partial · 26 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 +6 min
  • Mon 12 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to — +4 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 84% · 16
  • 3–10 min 16% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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