Train NS 8962 Utrecht Centraal – Bodegraven

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:05 from Utrecht Centraal · Thu 5 Nov

Next departure 18:05 today · Utrecht Centraal
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 13 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 5 full · 4 partial · 46 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: +4 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 +11 min · last fix heading to Utrecht Leidsche Rijn +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 50% W n=2
  • 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).

Last 90 days, 9 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
18:05on time on time
18:09≈ on time ≈ +1 min
18:11≈ on time ≈ +2 min
18:15≈ on time ≈ +3 min
18:21 / 18:22≈ on time ≈ +4 min
18:30+1 min +6 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 4 NovUtrecht Centraal 18:29No data—
Tue 3 NovUtrecht Terwijde 18:29No data—
Mon 2 NovUtrecht Leidsche Rijn 18:29No data—
Fri 30 OctWoerden 18:36Partial coverage0 min—
Thu 29 Oct— 18:33No data—
Wed 28 OctUtrecht Terwijde 18:32Partial coverage0 min—
Tue 27 OctUtrecht Centraal 18:32Partial coverage0 min—
Mon 26 OctUtrecht Leidsche Rijn 18:31No data—
Fri 23 OctWoerden 18:36No data—
Thu 22 OctWoerden 18:36No data—
Wed 21 OctWoerden 18:34No data—
Tue 20 OctWoerden 18:36No data—
Fri 16 Oct— 18:28No data—
Thu 15 OctWoerden 18:36No data—
Wed 14 OctWoerden 18:37No data—
Tue 13 OctWoerden 18:36No data—
Mon 12 OctWoerden 18:32Partial coverage0 min—
Fri 9 OctBodegraven 18:56+1 min—
Thu 8 Oct— 18:540 min—
Wed 7 OctUtrecht Leidsche Rijn 19:12+10 min+11 min
Tue 6 Oct— 18:550 min+1 min
Mon 5 OctUtrecht Terwijde 18:53+1 min—
Fri 2 OctLeiden Lammenschans 19:01No data—
Thu 1 OctUtrecht Centraal 18:19No data—
Wed 30 SeptUtrecht Leidsche Rijn 18:18No data—
Tue 29 SeptUtrecht Centraal 18:19No data—
Mon 28 SeptUtrecht Centraal 18:19No data—
Fri 25 SeptBodegraven 18:45No data—
Wed 23 SeptUtrecht Terwijde 18:25No data—
Mon 21 SeptUtrecht Centraal 18:19No data—