Train NS 6778 Tiel – Bodegraven
Running now · updated 21:25
Heading to Bodegraven 0 min
Estimated arrival at Bodegraven 22:15 · 138 km/h
- Tiel21:18
- Geldermalsen21:29
- Culemborg21:35
- Houten21:45
- Utrecht Vaartsche Rijn21:52
- Utrecht Centraal21:55
- Bodegraven22:15
Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 16 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
- Mon 2 Nov Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 18
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=3
- 100% W n=3
- 100% T n=2
- 100% F n=4
- 100% S n=1
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 19 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 |
|---|---|---|---|---|
| 21:18 | on time | on time | ||
| 21:21 | ≈ on time | ≈ on time | ||
| 21:29 / 21:30 | ≈ on time | ≈ on time | ||
| 21:35 | ≈ on time | ≈ on time | ||
| 21:41 / 21:42 | ≈ on time | ≈ +1 min | ||
| 21:45 | ≈ on time | ≈ +1 min | ||
| 21:49 | ≈ on time | ≈ +1 min | ||
| 21:52 | ≈ on time | ≈ +1 min | ||
| 21:55 / 21:56 | ≈ on time | ≈ +1 min | ||
| 22:06 / 22:07 | ≈ on time | ≈ +1 min | ||
| 22:15 | on time | +2 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 | — 21:24 | 0 min | — |
| Wed 4 Nov | — 22:14 | 0 min | — |
| Tue 3 Nov | — 22:14 | No data | — |
| Mon 2 Nov | — 22:19 | +3 min | +3 min |
| Sun 1 Nov | Woerden 22:19Partial coverage | 0 min | — |
| Sat 31 Oct | Woerden 22:21 | No data | — |
| Fri 30 Oct | — 22:18 | No data | — |
| Thu 29 Oct | — 22:17 | +1 min | — |
| Wed 28 Oct | — 22:17 | 0 min | — |
| Tue 27 Oct | — 22:17 | 0 min | — |
| Mon 26 Oct | — 22:16 | No data | — |
| Sun 25 Oct | Woerden 22:21 | No data | — |
| Sat 24 Oct | Woerden 22:18 | No data | — |
| Fri 23 Oct | — 22:16 | 0 min | — |
| Thu 22 Oct | — 22:17 | No data | — |
| Wed 21 Oct | — 22:17 | No data | — |
| Tue 20 Oct | — 22:17 | 0 min | — |
| Mon 19 Oct | — 21:57 | No data | — |
| Sun 18 Oct | Utrecht Vaartsche Rijn 22:06 | 0 min | — |
| Sat 17 Oct | Woerden 22:21 | No data | — |
| Fri 16 Oct | — 21:43 | 0 min | — |
| Thu 15 Oct | — 22:18 | No data | — |
| Wed 14 Oct | — 22:16 | No data | — |
| Tue 13 Oct | — 22:17 | No data | — |
| Mon 12 Oct | — 22:16 | 0 min | — |
| Sun 11 Oct | Leiden Lammenschans 22:47 | 0 min | — |
| Sat 10 Oct | Utrecht Centraal 22:39 | 0 min | +1 min |
| Fri 9 Oct | — 22:39 | +1 min | +1 min |
| Thu 8 Oct | — 22:40 | +1 min | +1 min |
| Wed 7 Oct | — 22:39 | +2 min | +2 min |