Train NS 11409 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 02:10 → Rotterdam Centraal 04:27 Wed 2 h 17 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 8 October 0 min

On-time · 30 days
—
Too little data (1/4 runs with data)
RT coverage: 0 full · 1 partial · 3 no data
On-time · 90 days
—
Too little data (1/13 runs with data)
RT coverage: 0 full · 1 partial · 12 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

Last 30 days

Arrival delay at Rotterdam 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

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

  • Early 0% · 0
  • On time 100% · 1
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
02:10
02:44 / 02:46
03:01 / 03:05
03:21 / 03:23
03:37 / 03:44
04:27

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
Thu 8 OctGouda 04:28Partial coverage0 min—
Thu 1 OctGouda 04:25No data—
Thu 24 SeptGouda 04:24No data—
Thu 17 SeptGouda 04:26No data—
Sun 13 SeptSchiedam Centrum 04:08No data—
Thu 3 SeptGouda 04:27No data—
Thu 27 AugGouda 04:25No data—
Fri 21 AugGouda 04:24No data—
Thu 20 AugGouda 04:26No data—
Thu 13 AugGouda 04:38No data—
Thu 6 AugGouda 04:25No data—
Thu 30 JulGouda 04:25No data—
Thu 23 JulGouda 04:31No data—