Train NS 6735 Bodegraven – Tiel

Bodegraven 10:16 → Tiel 11:12 Fri, Sat, Sun 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tiel Passewaaij at 11:23 No data

  1. Bodegraven10:16
  2. Utrecht Centraal10:33
  3. Utrecht Vaartsche Rijn10:37
  4. Houten10:43
  5. Culemborg10:53
  6. Tiel Passewaaij11:08
  7. Tiel11:12

Next service: Friday 10:16 from Bodegraven · Fri 13 Nov

Next departure 10:16 Friday · Bodegraven
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 5 full · 3 partial · 5 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 5 full · 3 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sat 24 Oct Max en route +4 min · last fix heading to Zaltbommel +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=2
  • 67% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 8 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
10:16on time on time
10:23≈ on time ≈ on time
10:33 / 10:35≈ on time ≈ +1 min
10:37≈ on time ≈ +1 min
10:40≈ on time ≈ +1 min
10:43 / 10:44≈ on time ≈ +1 min
10:47≈ +1 min ≈ +2 min
10:53≈ +1 min ≈ +2 min
11:00 / 11:01≈ +1 min ≈ +2 min
11:08≈ +1 min ≈ +3 min
11:12+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 NovTiel Passewaaij 11:23No data—
Sun 1 NovTiel Passewaaij 11:24Partial coverage0 min—
Sat 31 OctTiel Passewaaij 11:23Partial coverage0 min+1 min
Fri 30 OctTiel Passewaaij 11:23No data—
Sun 25 OctTiel Passewaaij 11:23No data—
Sat 24 OctZaltbommel 11:36+4 min+4 min
Fri 23 OctZaltbommel 11:35No data—
Sun 18 OctTiel Passewaaij 11:23+1 min—
Sat 17 OctTiel Passewaaij 11:24No data—
Fri 16 OctTiel Passewaaij 11:23Partial coverage0 min—
Sun 11 OctTiel Passewaaij 11:220 min—
Sat 10 OctTiel Passewaaij 11:24+1 min+1 min
Fri 9 OctTiel Passewaaij 11:220 min—
Mon 5 OctTiel Passewaaij 11:24No data—
Sun 4 OctTiel Passewaaij 11:33No data—
Sat 3 OctTiel Passewaaij 11:24No data—
Fri 2 OctTiel Passewaaij 11:28No data—
Sun 27 SeptTiel Passewaaij 11:23No data—
Sat 26 SeptTiel Passewaaij 11:23No data—
Fri 25 SeptTiel Passewaaij 11:23No data—
Sun 20 SeptTiel Passewaaij 11:23No data—
Sat 19 SeptTiel Passewaaij 11:23No data—
Fri 18 SeptTiel Passewaaij 11:23No data—
Sun 13 SeptTiel Passewaaij 11:23No data—
Sat 12 SeptTiel Passewaaij 11:23No data—
Fri 11 SeptTiel Passewaaij 11:23No data—
Sun 6 SeptTiel Passewaaij 11:22No data—
Sat 5 SeptTiel Passewaaij 11:22No data—
Fri 4 SeptTiel Passewaaij 11:23No data—
Sun 30 AugTiel Passewaaij 11:23No data—