Train NS 8954 Utrecht Centraal – Bodegraven

Utrecht Centraal 16:05 → Bodegraven 16:30 Mon, Tue, Wed, Thu, Fri 0 h 25 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Woerden at 16:36 No data

  1. Utrecht Centraal16:05
  2. Utrecht Leidsche Rijn16:09
  3. Utrecht Terwijde16:11
  4. Vleuten16:15
  5. Woerden16:21
  6. Bodegraven16:30

Next service: tomorrow 16:05 from Utrecht Centraal · Fri 30 Oct

Full trip card
Next departure 16:05 tomorrow · Utrecht Centraal
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 14 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=2
  • 100% W n=1
  • 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).

StopSched.
Utrecht Centraal
16:05
Utrecht Leidsche Rijn
16:09
Utrecht Terwijde
16:11
Vleuten
16:15
Woerden
16:21 / 16:22
Bodegraven
16: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

DateLast stopFinalMax
Thu 29 OctWoerden 16:36No data—
Wed 28 OctWoerden 16:36No data—
Tue 27 OctWoerden 16:37Partial coverage0 min—
Mon 26 OctWoerden 16:36No data—
Fri 23 OctWoerden 16:36No data—
Thu 22 OctWoerden 16:36No data—
Wed 21 OctWoerden 16:36No data—
Tue 20 OctWoerden 16:36No data—
Fri 16 OctWoerden 16:36No data—
Thu 15 OctWoerden 16:36No data—
Wed 14 OctWoerden 16:36No data—
Tue 13 OctWoerden 16:36No data—
Mon 12 OctWoerden 16:37Partial coverage+1 min+1 min
Fri 9 OctLeiden Lammenschans 17:03+1 min+1 min
Thu 8 OctLeiden Lammenschans 17:010 min—
Wed 7 OctLeiden Lammenschans 17:01+1 min+1 min
Tue 6 OctLeiden Lammenschans 17:010 min—
Mon 5 OctLeiden Lammenschans 17:010 min—
Fri 2 OctLeiden Lammenschans 17:04No data—
Thu 1 OctLeiden Lammenschans 17:01No data—
Wed 30 SeptLeiden Lammenschans 17:01No data—
Tue 29 SeptLeiden Lammenschans 17:01No data—
Mon 28 SeptLeiden Lammenschans 17:02No data—
Fri 25 SeptLeiden Lammenschans 17:03No data—
Thu 24 SeptLeiden Lammenschans 17:01No data—
Wed 23 SeptLeiden Lammenschans 17:01No data—
Tue 22 SeptLeiden Lammenschans 17:01No data—
Mon 21 SeptLeiden Lammenschans 17:01No data—
Fri 18 SeptLeiden Lammenschans 17:03No data—
Thu 17 SeptLeiden Lammenschans 16:57No data—