Train NS 6787 Bodegraven – Tiel

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:16 from Bodegraven · Fri 6 Nov

Full trip card
Next departure 23:16 today · Bodegraven
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 21 full · 3 partial · 4 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 24 full · 3 partial · 20 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

  • Wed 7 Oct Max en route +5 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 80% W n=5
  • 100% T n=3
  • 100% F n=3
  • 75% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 27 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
Bodegraven
23:16on time on time
Woerden
23:23≈ on time ≈ on time
Utrecht Centraal
23:33 / 23:35≈ on time ≈ +1 min
Utrecht Vaartsche Rijn
23:37≈ on time ≈ +1 min
Utrecht Lunetten
23:40≈ on time ≈ +1 min
Houten
23:43 / 23:44≈ on time ≈ +1 min
Houten Castellum
23:47≈ on time ≈ +1 min
Culemborg
23:53≈ on time ≈ +2 min
Geldermalsen
00:00 / 00:01≈ on time ≈ +2 min
Tiel Passewaaij
00:08≈ on time ≈ +2 min
Tiel
00: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
Thu 5 Nov— 00:22No data—
Wed 4 Nov— 00:19+2 min+2 min
Tue 3 Nov— 00:140 min—
Sun 1 NovTiel Passewaaij 00:23Partial coverage0 min—
Sat 31 OctBodegraven 00:17Partial coverage0 min—
Fri 30 Oct— 00:18No data—
Thu 29 Oct— 00:16+2 min+2 min
Wed 28 Oct— 00:160 min—
Tue 27 Oct— 00:220 min—
Mon 26 Oct— 00:130 min—
Sun 25 OctTiel Passewaaij 00:23No data—
Sat 24 Oct— 00:290 min—
Fri 23 Oct— 00:290 min—
Thu 22 Oct— 00:15No data—
Wed 21 Oct— 00:240 min—
Tue 20 Oct— 00:130 min—
Mon 19 Oct— 00:160 min—
Sun 18 OctTiel Passewaaij 00:230 min—
Sat 17 OctTiel Passewaaij 00:220 min—
Fri 16 Oct— 00:19+2 min+2 min
Thu 15 Oct— 00:160 min—
Wed 14 Oct— 00:130 min—
Tue 13 Oct— 00:200 min—
Mon 12 Oct— 00:20+3 min+3 min
Sun 11 OctGeldermalsen 00:32Partial coverage0 min+5 min
Sat 10 Oct— 00:21+4 min+4 min
Fri 9 Oct— 00:150 min—
Thu 8 Oct— 00:13+1 min—
Wed 7 Oct— 00:22+4 min+5 min
Tue 6 Oct— 23:450 min—