Train NS 8937 Bodegraven – Utrecht Centraal
✓ Today’s run finished
Today, last fix heading to Utrecht Leidsche Rijn at 11:09 No data
- Bodegraven10:31
- Woerden10:39
- Vleuten10:50
- Utrecht Terwijde10:53
- Utrecht Leidsche Rijn10:56
- Utrecht Centraal11:01
Next service: tomorrow 10:31 from Bodegraven · Fri 6 Nov
Last 30 days
Arrival delay at Utrecht Centraal, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 15
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=3
- 100% W n=3
- 100% T n=3
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 15 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 |
|---|---|---|---|
| 10:31 | on time | on time | |
| 10:39 / 10:44 | — | — | |
| 10:50 | — | — | |
| 10:53 | — | — | |
| 10:56 | — | — | |
| 11:01 | — | — |
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 |
|---|---|---|---|
| Thu 5 Nov | Utrecht Leidsche Rijn 11:09 | No data | — |
| Wed 4 Nov | Utrecht Leidsche Rijn 11:09Partial coverage | 0 min | — |
| Tue 3 Nov | Utrecht Leidsche Rijn 11:09 | No data | — |
| Mon 2 Nov | Utrecht Leidsche Rijn 11:09Partial coverage | 0 min | — |
| Fri 30 Oct | Utrecht Leidsche Rijn 11:11Partial coverage | 0 min | — |
| Thu 29 Oct | Utrecht Leidsche Rijn 11:10Partial coverage | 0 min | — |
| Wed 28 Oct | Utrecht Leidsche Rijn 11:11Partial coverage | 0 min | — |
| Tue 27 Oct | Utrecht Leidsche Rijn 11:10Partial coverage | 0 min | — |
| Mon 26 Oct | Utrecht Leidsche Rijn 11:10Partial coverage | 0 min | — |
| Fri 23 Oct | Utrecht Leidsche Rijn 11:10Partial coverage | 0 min | — |
| Thu 22 Oct | Utrecht Leidsche Rijn 11:18 | No data | — |
| Wed 21 Oct | Utrecht Leidsche Rijn 11:11 | No data | — |
| Tue 20 Oct | Utrecht Leidsche Rijn 11:11Partial coverage | 0 min | — |
| Fri 16 Oct | Utrecht Leidsche Rijn 11:10 | No data | — |
| Thu 15 Oct | Utrecht Leidsche Rijn 11:11Partial coverage | 0 min | — |
| Wed 14 Oct | Utrecht Leidsche Rijn 11:11Partial coverage | 0 min | — |
| Tue 13 Oct | Utrecht Leidsche Rijn 11:10 | No data | — |
| Mon 12 Oct | Utrecht Leidsche Rijn 11:10Partial coverage | 0 min | — |
| Fri 9 Oct | Utrecht Leidsche Rijn 11:10 | +1 min | +1 min |
| Thu 8 Oct | Utrecht Leidsche Rijn 11:10 | 0 min | — |
| Wed 7 Oct | Utrecht Terwijde 12:05 | No data | — |
| Tue 6 Oct | Utrecht Leidsche Rijn 11:10 | 0 min | — |
| Mon 5 Oct | Utrecht Leidsche Rijn 11:10 | No data | — |
| Fri 2 Oct | Utrecht Leidsche Rijn 11:11 | No data | — |
| Thu 1 Oct | Utrecht Leidsche Rijn 11:10 | No data | — |
| Wed 30 Sept | Utrecht Leidsche Rijn 11:27 | No data | — |
| Tue 29 Sept | Utrecht Leidsche Rijn 11:10 | No data | — |
| Mon 28 Sept | Utrecht Leidsche Rijn 11:10 | No data | — |
| Fri 25 Sept | Utrecht Leidsche Rijn 11:10 | No data | — |
| Thu 24 Sept | Utrecht Leidsche Rijn 11:10 | No data | — |