Train NS 8922 Utrecht Centraal – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 08:36 0 min
- Utrecht Centraal08:05
- Utrecht Leidsche Rijn08:09
- Utrecht Terwijde08:11
- Vleuten08:15
- Woerden08:21
- Bodegraven08:30
Next service: Monday 08:05 from Utrecht Centraal · Mon 2 Nov
Next departure 08:05 Monday · Utrecht Centraal
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 4 full · 3 partial · 14 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 4 full · 3 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min
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
- Wed 7 Oct Max en route +5 min · last fix heading to Leiden Lammenschans +4 min
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 6
- 3–10 min 14% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=2
- 0% W n=1
- 100% T n=1
- 100% F n=2
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
| Stop | Sched. |
|---|---|
| 08:05 | |
| 08:09 | |
| 08:11 | |
| 08:15 | |
| 08:21 / 08:22 | |
| 08:30 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 30 Oct | Woerden 08:36Partial coverage | 0 min | — |
| Thu 29 Oct | Woerden 08:36 | No data | — |
| Wed 28 Oct | Woerden 08:36 | No data | — |
| Tue 27 Oct | Woerden 08:36Partial coverage | 0 min | — |
| Mon 26 Oct | Woerden 08:36 | No data | — |
| Fri 23 Oct | Woerden 08:36 | No data | — |
| Thu 22 Oct | Woerden 08:36 | No data | — |
| Wed 21 Oct | Woerden 08:36 | No data | — |
| Tue 20 Oct | Woerden 08:36 | No data | — |
| Fri 16 Oct | Woerden 08:36 | No data | — |
| Thu 15 Oct | Woerden 08:36 | No data | — |
| Wed 14 Oct | Woerden 08:36 | No data | — |
| Tue 13 Oct | Woerden 08:36 | No data | — |
| Mon 12 Oct | Woerden 08:36Partial coverage | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 09:02 | 0 min | — |
| Thu 8 Oct | Leiden Lammenschans 09:02 | +1 min | — |
| Wed 7 Oct | Leiden Lammenschans 09:06 | +4 min | +5 min |
| Tue 6 Oct | Leiden Lammenschans 09:04 | +2 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 09:02 | No data | — |
| Fri 2 Oct | Leiden Lammenschans 09:03 | No data | — |
| Thu 1 Oct | Leiden Lammenschans 09:03 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 09:03 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 09:03 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 09:03 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 09:02 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 09:03 | No data | — |
| Wed 23 Sept | Leiden Lammenschans 09:03 | No data | — |
| Tue 22 Sept | Leiden Lammenschans 09:02 | No data | — |
| Mon 21 Sept | Leiden Lammenschans 09:03 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 09:02 | No data | — |