Train NS 2028 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 10:18 → Rotterdam Centraal 10:55 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November +1 min

Next service: today 10:18 from Utrecht Centraal · Sat 14 Nov

Next departure 10:18 today · Utrecht Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 3 full · 12 partial · 5 no data
On-time · 90 days
95%
42/44 runs under 3 min
RT coverage: 27 full · 17 partial · 26 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 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

  • Tue 10 Nov Max en route +12 min · last fix heading to Rotterdam Alexander +12 min
  • Sat 29 Aug Max en route +5 min · last fix heading to Rotterdam Alexander +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=8
  • 86% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 86% S n=7
  • 100% S n=1

Stops and timetable

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

Last 90 days, 44 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:18on time on time
10:36 / 10:37≈ on time ≈ on time
10:46≈ on time ≈ +1 min
10:55on 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
Fri 13 NovRotterdam Alexander 11:02Partial coverage+1 min+2 min
Thu 12 NovRotterdam Alexander 11:00Partial coverage0 min—
Wed 11 NovRotterdam Alexander 10:59Partial coverage0 min—
Tue 10 NovRotterdam Alexander 11:13Partial coverage+12 min+12 min
Mon 9 NovRotterdam Alexander 10:59Partial coverage0 min—
Sun 8 NovDelft 11:220 min—
Sat 7 NovDelft 11:220 min+1 min
Fri 6 NovRotterdam Alexander 10:59No data—
Thu 5 NovRotterdam Alexander 10:59No data—
Wed 4 NovRotterdam Alexander 10:59Partial coverage0 min—
Tue 3 NovRotterdam Alexander 10:59No data—
Mon 2 NovRotterdam Alexander 10:59No data—
Sat 31 OctRotterdam Alexander 11:02Partial coverage+1 min+4 min
Fri 30 OctRotterdam Alexander 11:00Partial coverage0 min—
Thu 29 OctRotterdam Alexander 11:01Partial coverage0 min—
Wed 28 OctRotterdam Alexander 11:01No data—
Tue 27 OctRotterdam Alexander 11:02Partial coverage0 min—
Mon 26 OctRotterdam Alexander 11:00Partial coverage0 min—
Sat 17 OctDelft 11:200 min—
Fri 16 OctRotterdam Alexander 11:01Partial coverage0 min—
Thu 15 OctRotterdam Alexander 11:02No data—
Wed 14 OctRotterdam Alexander 11:01No data—
Tue 13 OctRotterdam Alexander 11:02No data—
Mon 12 OctRotterdam Alexander 11:01Partial coverage0 min—
Sat 10 OctRotterdam Alexander 11:01Partial coverage0 min—
Fri 9 OctRotterdam Alexander 11:01Partial coverage0 min—
Thu 8 OctRotterdam Alexander 11:01Partial coverage+1 min—
Wed 7 OctGouda 12:030 min—
Tue 6 OctRotterdam Alexander 11:00Partial coverage0 min—
Mon 5 OctRotterdam Alexander 12:20−1 min—