Train NS 6760 Tiel – Bodegraven
Running now · updated 17:00
Heading to Bodegraven 0 min
Estimated arrival at Bodegraven 17:45 · 49 km/h
- Tiel16:48
- Geldermalsen16:59
- Culemborg17:05
- Houten17:15
- Utrecht Vaartsche Rijn17:22
- Utrecht Centraal17:25
- Bodegraven17:45
Today it is running no worse than usual: typical arrival delay is 0 min; 91% of the last 11 runs arrived on time.
Last 30 days
Arrival delay at Bodegraven, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 13 Nov Max en route +6 min · last fix heading to Woerden +6 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 94% · 15
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- 83% F n=6
- 100% S n=5
- 100% S n=4
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.
| Stop | Sched. | Usually | 9 days in 10 | Today |
|---|---|---|---|---|
| 16:48 | on time | on time | ||
| 16:51 | ≈ on time | ≈ on time | ||
| 16:59 / 17:00 | ≈ on time | ≈ on time | ||
| 17:05 | ≈ on time | ≈ on time | ||
| 17:11 / 17:12 | ≈ on time | ≈ on time | ||
| 17:15 | ≈ on time | ≈ on time | ||
| 17:19 | ≈ on time | ≈ on time | ||
| 17:22 | ≈ on time | ≈ on time | ||
| 17:25 / 17:26 | ≈ on time | ≈ on time | ||
| 17:36 / 17:37 | ≈ on time | ≈ +1 min | ||
| 17:45 | on time | +1 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 15 Nov | Geldermalsen 16:59Partial coverage | 0 min | — |
| Sat 14 Nov | Woerden 17:49Partial coverage | 0 min | — |
| Fri 13 Nov | Woerden 17:58 | +6 min | +6 min |
| Fri 6 Nov | Woerden 17:49 | 0 min | — |
| Sun 1 Nov | Woerden 17:54Partial coverage | +2 min | +5 min |
| Sat 31 Oct | Woerden 17:54Partial coverage | +2 min | +4 min |
| Fri 30 Oct | Woerden 17:56 | 0 min | — |
| Sun 25 Oct | Woerden 17:52 | No data | — |
| Sat 24 Oct | Woerden 17:48 | 0 min | — |
| Fri 23 Oct | Woerden 17:51 | 0 min | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 17:37 | 0 min | — |
| Sat 17 Oct | Woerden 17:51Partial coverage | 0 min | — |
| Fri 16 Oct | Woerden 17:54 | 0 min | — |
| Sun 11 Oct | Leiden Lammenschans 18:17 | 0 min | — |
| Sat 10 Oct | Leiden Lammenschans 18:17 | +1 min | — |
| Fri 9 Oct | Leiden Lammenschans 18:16 | 0 min | — |
| Mon 5 Oct | Leiden Lammenschans 18:16 | +1 min | — |
| Sun 4 Oct | Leiden Lammenschans 18:17 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 18:18 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 18:16 | No data | — |
| Sun 27 Sept | Leiden Lammenschans 18:17 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 18:18 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 18:16 | No data | — |
| Sun 20 Sept | Leiden Lammenschans 18:18 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 18:28 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 18:16 | No data | — |
| Sun 13 Sept | Leiden Lammenschans 18:17 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 18:18 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 18:16 | No data | — |
| Sun 6 Sept | Leiden Lammenschans 18:17 | No data | — |