Train NS 2030 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 10:48 → Rotterdam Centraal 11:25 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Rotterdam Alexander at 11:29 0 min

  1. Utrecht Centraal10:48
  2. Gouda11:06
  3. Rotterdam Alexander11:16
  4. Rotterdam Centraal11:25

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

Next departure 10:48 tomorrow · Utrecht Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 1 full · 14 partial · 7 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 30 full · 15 partial · 34 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: 0 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

  • Sun 20 Sept Max en route +19 min · last fix heading to Rotterdam Alexander +18 min
  • Sun 1 Nov Max en route +17 min · last fix heading to Rotterdam Alexander +17 min

Distribution · 90 days

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

  • Early 24% · 11
  • On time 71% · 32
  • 3–10 min 0% · 0
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=6
  • 100% T n=7
  • 100% F n=7
  • 100% S n=5
  • 60% S n=5

Stops and timetable

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

Last 90 days, 45 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
10:48on time on time
11:06 / 11:07≈ on time ≈ on time
11:16≈ on time ≈ on time
11:25on time on time

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 11:29Partial coverage0 min—
Wed 4 NovRotterdam Alexander 11:29Partial coverage0 min—
Tue 3 NovRotterdam Alexander 11:43No data—
Mon 2 NovRotterdam Alexander 11:29No data—
Sun 1 NovRotterdam Alexander 11:48Partial coverage+17 min+17 min
Sat 31 OctRotterdam Alexander 11:31Partial coverage+1 min—
Fri 30 OctRotterdam Alexander 11:31No data—
Thu 29 OctRotterdam Alexander 11:31No data—
Wed 28 OctRotterdam Alexander 11:31Partial coverage0 min—
Tue 27 OctRotterdam Alexander 11:31Partial coverage0 min—
Mon 26 OctRotterdam Alexander 11:32Partial coverage0 min—
Sat 17 OctDelft 11:480 min—
Fri 16 OctRotterdam Alexander 11:32No data—
Thu 15 OctRotterdam Alexander 11:31No data—
Wed 14 OctRotterdam Alexander 11:31No data—
Tue 13 OctRotterdam Alexander 11:31Partial coverage0 min—
Mon 12 OctRotterdam Alexander 11:32Partial coverage0 min—
Sun 11 OctRotterdam Alexander 11:31Partial coverage0 min—
Sat 10 OctRotterdam Alexander 11:30Partial coverage0 min—
Fri 9 OctRotterdam Alexander 11:31Partial coverage0 min—
Thu 8 OctRotterdam Alexander 11:30Partial coverage0 min—
Wed 7 OctGouda 12:03Partial coverage0 min—
Tue 6 OctRotterdam Alexander 11:31Partial coverage0 min—
Mon 5 OctRotterdam Alexander 11:31No data—
Sun 4 OctRotterdam Alexander 11:31No data—
Sat 3 OctRotterdam Alexander 11:32No data—
Fri 2 OctRotterdam Alexander 11:31No data—
Thu 1 OctRotterdam Alexander 11:31No data—
Wed 30 SeptRotterdam Alexander 11:37No data—
Tue 29 SeptRotterdam Alexander 11:31No data—