Train NS 8950 Utrecht Centraal – Bodegraven
✓ Today’s run finished
Today, last fix heading to Woerden at 15:36 0 min
- Utrecht Centraal15:05
- Utrecht Leidsche Rijn15:09
- Utrecht Terwijde15:11
- Vleuten15:15
- Woerden15:21
- Bodegraven15:30
Next service: tomorrow 15:05 from Utrecht Centraal · Thu 15 Oct
Next departure 15:05 tomorrow · Utrecht Centraal
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 15 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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
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 100% · 7
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=1
- 100% W n=2
- 100% T n=1
- 100% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
| Stop | Sched. |
|---|---|
| 15:05 | |
| 15:09 | |
| 15:11 | |
| 15:15 | |
| 15:21 / 15:22 | |
| 15: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 |
|---|---|---|---|
| Wed 14 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Tue 13 Oct | Woerden 15:36 | No data | — |
| Mon 12 Oct | Woerden 15:36Partial coverage | 0 min | — |
| Fri 9 Oct | Leiden Lammenschans 16:03 | +1 min | +2 min |
| Thu 8 Oct | Leiden Lammenschans 16:02 | 0 min | — |
| Wed 7 Oct | Leiden Lammenschans 16:02 | +1 min | +3 min |
| Tue 6 Oct | Leiden Lammenschans 16:04 | +2 min | +2 min |
| Mon 5 Oct | Leiden Lammenschans 16:02 | 0 min | — |
| Fri 2 Oct | Leiden Lammenschans 16:04 | No data | — |
| Thu 1 Oct | Leiden Lammenschans 16:03 | No data | — |
| Wed 30 Sept | Leiden Lammenschans 16:02 | No data | — |
| Tue 29 Sept | Leiden Lammenschans 16:02 | No data | — |
| Mon 28 Sept | Leiden Lammenschans 16:03 | No data | — |
| Fri 25 Sept | Leiden Lammenschans 16:02 | No data | — |
| Thu 24 Sept | Leiden Lammenschans 16:02 | No data | — |
| Wed 23 Sept | Leiden Lammenschans 16:05 | No data | — |
| Tue 22 Sept | Leiden Lammenschans 16:02 | No data | — |
| Mon 21 Sept | Leiden Lammenschans 16:02 | No data | — |
| Fri 18 Sept | Leiden Lammenschans 16:03 | No data | — |
| Thu 17 Sept | Leiden Lammenschans 16:02 | No data | — |
| Wed 16 Sept | Leiden Lammenschans 16:04 | No data | — |
| Tue 15 Sept | Leiden Lammenschans 16:02 | No data | — |
| Mon 14 Sept | Leiden Lammenschans 16:05 | No data | — |
| Fri 11 Sept | Leiden Lammenschans 16:02 | No data | — |
| Thu 10 Sept | Leiden Lammenschans 16:02 | No data | — |
| Tue 8 Sept | Leiden Lammenschans 16:02 | No data | — |
| Mon 7 Sept | Leiden Lammenschans 16:02 | No data | — |
| Fri 4 Sept | Leiden Lammenschans 16:03 | No data | — |
| Thu 3 Sept | Leiden Lammenschans 16:02 | No data | — |
| Wed 2 Sept | Leiden Lammenschans 16:05 | No data | — |