Train NS 6758 Tiel – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 17:19 0 min
- Tiel16:18
- Geldermalsen16:29
- Culemborg16:35
- Houten16:45
- Utrecht Vaartsche Rijn16:52
- Woerden17:06
- Bodegraven17:15
Next service: Friday 16:18 from Tiel · Fri 13 Nov
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
- Sat 24 Oct Max en route +5 min · last fix heading to Woerden +5 min
Distribution · 90 days
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 10
- 3–10 min 9% · 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
- 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, 11 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 |
|---|---|---|---|
| 16:18 | on time | on time | |
| 16:21 | ≈ on time | ≈ on time | |
| 16:29 / 16:30 | ≈ on time | ≈ +1 min | |
| 16:35 | ≈ on time | ≈ +1 min | |
| 16:41 / 16:42 | ≈ on time | ≈ +1 min | |
| 16:45 | ≈ on time | ≈ +1 min | |
| 16:49 | ≈ on time | ≈ +2 min | |
| 16:52 | ≈ on time | ≈ +2 min | |
| 16:55 / 16:56 | ≈ on time | ≈ +2 min | |
| 17:06 / 17:07 | ≈ on time | ≈ +2 min | |
| 17:15 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Woerden 17:19Partial coverage | 0 min | — |
| Sun 1 Nov | Woerden 17:21Partial coverage | 0 min | — |
| Sat 31 Oct | Woerden 17:23Partial coverage | +2 min | +4 min |
| Fri 30 Oct | Woerden 17:21Partial coverage | 0 min | — |
| Sun 25 Oct | Woerden 17:26 | No data | — |
| Sat 24 Oct | Woerden 17:23 | +5 min | +5 min |
| Fri 23 Oct | Woerden 17:22 | No data | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 17:07 | +1 min | — |
| Sat 17 Oct | Woerden 17:21Partial coverage | 0 min | — |
| Fri 16 Oct | Woerden 17:21 | No data | — |
| Sun 11 Oct | Leiden Lammenschans 17:46 | 0 min | — |
| Sat 10 Oct | Leiden Lammenschans 17:47 | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 17:52 | 0 min | +6 min |
| Mon 5 Oct | Leiden Lammenschans 17:46 | 0 min | — |
| Sun 4 Oct | Leiden Lammenschans 17:47 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 17:47 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 17:46 | No data | — |
| Sun 27 Sept | Leiden Lammenschans 18:00 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 17:47 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 17:46 | No data | — |
| Sun 20 Sept | Leiden Lammenschans 17:48 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 17:58 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 17:47 | No data | — |
| Sun 13 Sept | Leiden Lammenschans 17:48 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 17:47 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 17:54 | No data | — |
| Sun 6 Sept | Leiden Lammenschans 17:47 | No data | — |
| Sat 5 Sept | Leiden Lammenschans 17:48 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 17:46 | No data | — |
| Sun 30 Aug | Leiden Lammenschans 17:47 | No data | — |