Train NS 8927 Bodegraven – Utrecht Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 08:01 from Bodegraven · Thu 5 Nov

Next departure 08:01 today · Bodegraven
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 12 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

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 100% · 9
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
08:01on time on time
08:09 / 08:14— —
08:20— —
08:23— —
08:26— —
08:31— —

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 Leidsche Rijn 08:39Partial coverage0 min—
Tue 3 NovUtrecht Leidsche Rijn 08:39No data—
Mon 2 NovUtrecht Leidsche Rijn 08:39No data—
Fri 30 OctUtrecht Leidsche Rijn 08:40No data—
Thu 29 OctUtrecht Leidsche Rijn 08:40No data—
Wed 28 OctUtrecht Leidsche Rijn 08:44Partial coverage0 min—
Tue 27 OctUtrecht Leidsche Rijn 08:40Partial coverage0 min—
Mon 26 OctUtrecht Leidsche Rijn 08:41Partial coverage0 min—
Fri 23 OctUtrecht Leidsche Rijn 08:40No data—
Thu 22 OctUtrecht Leidsche Rijn 08:40No data—
Wed 21 OctUtrecht Leidsche Rijn 08:40No data—
Tue 20 OctBodegraven 09:01Partial coverage0 min—
Fri 16 OctUtrecht Leidsche Rijn 08:40No data—
Thu 15 OctUtrecht Leidsche Rijn 08:41No data—
Wed 14 OctUtrecht Leidsche Rijn 08:40No data—
Tue 13 OctUtrecht Leidsche Rijn 08:41No data—
Mon 12 OctUtrecht Leidsche Rijn 08:40No data—
Fri 9 OctUtrecht Leidsche Rijn 08:410 min—
Thu 8 OctUtrecht Leidsche Rijn 08:41+1 min+1 min
Wed 7 OctUtrecht Leidsche Rijn 08:420 min+1 min
Tue 6 OctUtrecht Leidsche Rijn 08:400 min—
Mon 5 OctUtrecht Leidsche Rijn 08:41No data—
Fri 2 OctUtrecht Leidsche Rijn 08:40No data—
Thu 1 OctUtrecht Leidsche Rijn 08:41No data—
Wed 30 SeptUtrecht Leidsche Rijn 08:40No data—
Tue 29 SeptUtrecht Leidsche Rijn 08:40No data—
Mon 28 SeptUtrecht Leidsche Rijn 08:41No data—
Fri 25 SeptUtrecht Leidsche Rijn 08:40No data—
Thu 24 SeptUtrecht Leidsche Rijn 08:40No data—
Wed 23 SeptUtrecht Leidsche Rijn 08:41No data—