Train NS 6754 Tiel – Bodegraven
It does not run today
Last recorded run: Friday 6 November No data
Next service: Friday 15: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 10 Oct Max en route +12 min · last fix heading to Leiden Lammenschans +12 min
Distribution · 90 days
9 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 8
- 3–10 min 0% · 0
- 10–30 min 11% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- 100% F n=1
- 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, 9 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 |
|---|---|---|---|
| 15:18 | on time | on time | |
| 15:21 | ≈ on time | ≈ on time | |
| 15:29 / 15:30 | ≈ on time | ≈ +1 min | |
| 15:35 | ≈ on time | ≈ +2 min | |
| 15:41 / 15:42 | ≈ on time | ≈ +3 min | |
| 15:45 | ≈ on time | ≈ +3 min | |
| 15:49 | ≈ on time | ≈ +4 min | |
| 15:52 | ≈ +1 min | ≈ +4 min | |
| 15:55 / 15:56 | ≈ +1 min | ≈ +5 min | |
| 16:06 / 16:07 | ≈ +1 min | ≈ +6 min | |
| 16:15 | +1 min | +7 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 16:19 | No data | — |
| Sun 1 Nov | Woerden 16:22Partial coverage | 0 min | — |
| Sat 31 Oct | Woerden 16:24Partial coverage | +3 min | +4 min |
| Fri 30 Oct | Woerden 16:21 | No data | — |
| Sun 25 Oct | Woerden 16:22 | No data | — |
| Sat 24 Oct | Woerden 16:21 | +3 min | +3 min |
| Fri 23 Oct | Woerden 16:21 | No data | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 16:07 | +1 min | — |
| Sat 17 Oct | Woerden 16:21Partial coverage | 0 min | — |
| Fri 16 Oct | Woerden 16:23 | No data | — |
| Sun 11 Oct | Leiden Lammenschans 16:47 | +1 min | — |
| Sat 10 Oct | Leiden Lammenschans 17:01 | +12 min | +12 min |
| Fri 9 Oct | Leiden Lammenschans 16:47 | 0 min | — |
| Mon 5 Oct | Leiden Lammenschans 16:47 | 0 min | — |
| Sun 4 Oct | Leiden Lammenschans 16:47 | No data | — |
| Sat 3 Oct | Leiden Lammenschans 16:48 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 16:47 | No data | — |
| Sun 27 Sept | Leiden Lammenschans 16:47 | No data | — |
| Sat 26 Sept | Leiden Lammenschans 16:47 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 16:47 | No data | — |
| Sun 20 Sept | Leiden Lammenschans 16:47 | No data | — |
| Sat 19 Sept | Leiden Lammenschans 16:47 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 16:47 | No data | — |
| Sun 13 Sept | Leiden Lammenschans 16:47 | No data | — |
| Sat 12 Sept | Leiden Lammenschans 16:48 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 16:49 | No data | — |
| Sun 6 Sept | Leiden Lammenschans 16:46 | No data | — |
| Sat 5 Sept | Leiden Lammenschans 16:47 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 16:47 | No data | — |
| Sun 30 Aug | Leiden Lammenschans 16:47 | No data | — |