Train NS 8914 Utrecht Centraal – Woerden

Utrecht Centraal 06:05 → Woerden 06:21 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:05 from Utrecht Centraal · Mon 9 Nov

Next departure 06:05 Monday · Utrecht Centraal
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 1 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 0 full · 22 partial · 40 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 Woerden, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 15 Oct Max en route +5 min · last fix heading to Vleuten +4 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Vleuten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 60% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 stops).

Last 90 days, 22 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
06:05on time on time
06:09— —
06:11— —
06:15— —
06:21— —

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
Fri 6 NovVleuten 06:29No data—
Thu 5 NovVleuten 06:29Partial coverage0 min—
Wed 4 NovVleuten 06:29Partial coverage+1 min+1 min
Tue 3 NovVleuten 06:29Partial coverage0 min—
Mon 2 NovVleuten 06:29Partial coverage0 min—
Fri 30 OctVleuten 06:29Partial coverage0 min—
Thu 29 OctVleuten 06:32Partial coverage+3 min+3 min
Wed 28 OctVleuten 06:29Partial coverage0 min—
Tue 27 OctVleuten 06:30Partial coverage+1 min+1 min
Mon 26 OctVleuten 06:29Partial coverage0 min—
Fri 23 OctVleuten 06:29Partial coverage0 min—
Thu 22 OctVleuten 06:29Partial coverage0 min—
Wed 21 OctVleuten 06:29Partial coverage0 min—
Tue 20 OctVleuten 06:29Partial coverage0 min—
Fri 16 OctVleuten 06:30Partial coverage0 min+2 min
Thu 15 OctVleuten 06:33Partial coverage+4 min+5 min
Wed 14 OctVleuten 06:29Partial coverage0 min—
Tue 13 OctVleuten 06:29Partial coverage0 min—
Mon 12 OctVleuten 06:30Partial coverage+1 min+1 min
Fri 9 OctVleuten 06:29Partial coverage0 min—
Thu 8 OctVleuten 06:30Partial coverage0 min—
Wed 7 OctVleuten 06:29Partial coverage0 min—
Tue 6 OctVleuten 06:29Partial coverage0 min—
Mon 5 OctVleuten 06:30No data—
Fri 2 OctVleuten 06:29No data—
Thu 1 OctVleuten 06:29No data—
Wed 30 SeptVleuten 06:29No data—
Tue 29 SeptVleuten 06:29No data—
Mon 28 SeptVleuten 06:29No data—
Fri 25 SeptVleuten 06:29No data—