Train NS 8814 Utrecht Centraal – Woerden

Utrecht Centraal 06:24 → Woerden 06:36 Mon, Tue, Wed, Thu 0 h 12 min · 3 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Utrecht Leidsche Rijn at 06:48 +5 min

  1. Utrecht Centraal06:24
  2. Utrecht Leidsche Rijn06:28
  3. Woerden06:36

Next service: tomorrow 06:24 from Utrecht Centraal · Tue 13 Oct

Next departure 06:24 tomorrow · Utrecht Centraal
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 2 full · 1 partial · 13 no data
On-time · 90 days
67%
2/3 runs under 3 min
RT coverage: 2 full · 1 partial · 48 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 so far)

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

  • Mon 12 Oct Max en route +5 min · last fix heading to Utrecht Leidsche Rijn +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 2
  • 3–10 min 33% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • 100% T n=1
  • 100% W n=1
  • — T n=0
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

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
Mon 12 OctUtrecht Leidsche Rijn 06:48Partial coverage+5 min+5 min
Thu 8 OctLeiden Lammenschans 07:17No data—
Wed 7 OctLeiden Lammenschans 07:17+1 min—
Tue 6 OctLeiden Lammenschans 07:170 min—
Thu 1 OctLeiden Lammenschans 07:18No data—
Wed 30 SeptLeiden Lammenschans 07:18No data—
Tue 29 SeptLeiden Lammenschans 07:17No data—
Mon 28 SeptLeiden Lammenschans 07:17No data—
Thu 24 SeptLeiden Lammenschans 07:30No data—
Wed 23 SeptLeiden Lammenschans 07:17No data—
Tue 22 SeptLeiden Lammenschans 07:17No data—
Mon 21 SeptLeiden Lammenschans 07:17No data—
Thu 17 SeptLeiden Lammenschans 07:17No data—
Wed 16 SeptLeiden Lammenschans 07:17No data—
Tue 15 SeptLeiden Lammenschans 07:17No data—
Mon 14 SeptLeiden Lammenschans 07:17No data—
Thu 10 SeptLeiden Lammenschans 07:17No data—
Tue 8 SeptLeiden Lammenschans 07:18No data—
Mon 7 SeptLeiden Lammenschans 07:18No data—
Thu 3 SeptLeiden Lammenschans 07:17No data—
Wed 2 SeptLeiden Lammenschans 07:18No data—
Tue 1 SeptLeiden Lammenschans 07:17No data—
Mon 31 AugLeiden Lammenschans 07:19No data—
Thu 27 AugLeiden Lammenschans 07:17No data—
Wed 26 AugLeiden Lammenschans 07:17No data—
Tue 25 AugLeiden Lammenschans 07:17No data—
Mon 24 AugLeiden Lammenschans 07:17No data—
Sat 22 AugLeiden Lammenschans 07:17No data—
Fri 21 AugLeiden Lammenschans 07:19No data—
Thu 20 AugLeiden Lammenschans 07:17No data—