Train NS 8971 Bodegraven – Utrecht Centraal

Bodegraven 19:01 → Utrecht Centraal 19:31 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 19:37 +3 min

  1. Bodegraven19:01
  2. Woerden19:09
  3. Vleuten19:20
  4. Utrecht Terwijde19:23
  5. Utrecht Leidsche Rijn19:26
  6. Utrecht Centraal19:31

Next service: tomorrow 19:01 from Bodegraven · Thu 12 Nov

Next departure 19:01 tomorrow · Bodegraven
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 12 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 12 full · 1 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

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

Worst days

  • Wed 7 Oct Max en route +15 min · last fix heading to — +15 min

Distribution · 90 days

13 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 0% · 0
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 50% W n=2
  • 100% T n=1
  • 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, 13 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.

StopSched.Usually 9 days in 10
19:01on time on time
19:09 / 19:14≈ on time ≈ +1 min
19:20≈ on time ≈ +2 min
19:23≈ on time ≈ +2 min
19:26≈ on time ≈ +2 min
19:31on 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

DateLast stopFinalMax
Wed 11 Nov— 19:37+3 min+4 min
Tue 10 Nov— 19:330 min—
Mon 9 Nov— 19:320 min—
Fri 6 Nov— 19:320 min—
Thu 5 Nov— 19:33No data—
Wed 4 Nov— 19:23No data—
Mon 2 Nov— 19:34No data—
Fri 30 Oct— 19:32No data—
Wed 28 Oct— 19:32No data—
Tue 27 Oct— 19:33No data—
Mon 26 Oct— 19:32No data—
Fri 23 OctUtrecht Leidsche Rijn 19:40Partial coverage0 min—
Thu 22 Oct— 19:33No data—
Wed 21 Oct— 19:33No data—
Tue 20 Oct— 19:320 min—
Fri 16 Oct— 19:15No data—
Thu 15 Oct— 19:35No data—
Wed 14 OctUtrecht Leidsche Rijn 19:40No data—
Tue 13 Oct— 19:330 min—
Mon 12 Oct— 19:320 min—
Fri 9 Oct— 19:320 min—
Thu 8 Oct— 19:320 min—
Wed 7 Oct— 20:02+15 min+15 min
Tue 6 Oct— 19:320 min—
Mon 5 Oct— 19:320 min—
Fri 2 OctLeiden Lammenschans 18:57No data—
Fri 18 SeptLeiden Lammenschans 18:57No data—
Fri 11 SeptLeiden Lammenschans 18:57No data—
Fri 4 SeptLeiden Lammenschans 18:57No data—
Fri 28 AugUtrecht Leidsche Rijn 19:40No data—