Train NS 2022 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 08:48 → Rotterdam Centraal 09:25 Mon, Tue, Wed, Thu, Fri, Sat 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Rotterdam Alexander at 09:29 No data

  1. Utrecht Centraal08:48
  2. Gouda09:06
  3. Rotterdam Alexander09:16
  4. Rotterdam Centraal09:25

Next service: tomorrow 08:48 from Utrecht Centraal · Fri 6 Nov

Next departure 08:48 tomorrow · Utrecht Centraal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 2 full · 10 partial · 5 no data
On-time · 90 days
98%
40/41 runs under 3 min
RT coverage: 30 full · 11 partial · 17 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: +2 min

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

Worst days

  • Wed 4 Nov Max en route +4 min · last fix heading to Rotterdam Alexander +4 min

Distribution · 90 days

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

  • Early 27% · 11
  • On time 71% · 29
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=6
  • 89% W n=9
  • 100% T n=8
  • 100% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 41 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:48on time on time
09:06 / 09:07≈ on time ≈ on time
09:16≈ on time ≈ +1 min
09:25on time +1 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
Thu 5 NovRotterdam Alexander 09:29No data—
Wed 4 NovRotterdam Alexander 09:34Partial coverage+4 min+4 min
Tue 3 NovRotterdam Alexander 09:37No data—
Mon 2 NovRotterdam Alexander 09:32No data—
Fri 30 OctRotterdam Alexander 09:32Partial coverage0 min—
Thu 29 OctRotterdam Alexander 09:32Partial coverage0 min—
Wed 28 OctRotterdam Alexander 09:310 min—
Tue 27 OctRotterdam Alexander 09:31Partial coverage0 min—
Mon 26 OctRotterdam Alexander 09:42Partial coverage0 min—
Fri 16 OctRotterdam Alexander 09:30Partial coverage0 min—
Thu 15 OctRotterdam Alexander 10:58No data—
Wed 14 OctRotterdam Alexander 09:310 min—
Tue 13 OctRotterdam Alexander 09:35No data—
Mon 12 OctRotterdam Alexander 09:32Partial coverage0 min—
Fri 9 OctRotterdam Alexander 09:33Partial coverage+2 min+2 min
Thu 8 OctRotterdam Alexander 09:33Partial coverage+2 min+3 min
Wed 7 OctRotterdam Alexander 09:31Partial coverage0 min—
Tue 6 OctRotterdam Alexander 09:31Partial coverage0 min—
Mon 5 OctRotterdam Alexander 09:31No data—
Fri 2 OctRotterdam Alexander 09:31No data—
Thu 1 OctRotterdam Alexander 09:31No data—
Wed 30 SeptRotterdam Alexander 09:310 min+4 min
Tue 29 SeptRotterdam Alexander 09:36No data—
Mon 28 SeptRotterdam Alexander 09:32No data—
Fri 25 SeptRotterdam Alexander 09:31No data—
Thu 24 SeptRotterdam Alexander 19:04+1 min+5 min
Wed 23 SeptRotterdam Alexander 23:42−4 min—
Tue 22 SeptRotterdam Alexander 09:32No data—
Mon 21 SeptRotterdam Alexander 14:460 min+7 min
Fri 18 SeptRotterdam Alexander 16:55−2 min+41 min