Train NS 2025 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 07:35 → Utrecht Centraal 08:12 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 07:35 from Rotterdam Centraal · Mon 9 Nov

Next departure 07:35 tomorrow · Rotterdam Centraal
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 0 full · 9 partial · 6 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 2 full · 11 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

  • Thu 29 Oct Max en route +7 min · last fix heading to Gouda +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 67% T n=3
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 13 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
07:35on time on time
07:43— —
07:53 / 07:54— —
08:12— —

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 6 NovGouda 08:14No data—
Thu 5 NovGouda 08:14No data—
Wed 4 NovGouda 08:14Partial coverage0 min—
Tue 3 NovGouda 08:08No data—
Mon 2 NovGouda 08:09No data—
Fri 30 OctGouda 08:15Partial coverage0 min—
Thu 29 OctGouda 08:27Partial coverage+7 min+7 min
Wed 28 OctGouda 08:14Partial coverage0 min—
Tue 27 OctGouda 08:16Partial coverage0 min—
Mon 26 OctGouda 08:15Partial coverage+2 min+3 min
Fri 16 OctGouda 08:14No data—
Thu 15 OctGouda 08:14Partial coverage0 min—
Wed 14 OctRotterdam Centraal 08:13No data—
Tue 13 OctRotterdam Centraal 08:35Partial coverage0 min—
Mon 12 OctGouda 08:15Partial coverage0 min—
Fri 9 OctGouda 08:13Partial coverage0 min—
Thu 8 OctGouda 08:18+2 min+3 min
Wed 7 OctGouda 08:130 min—
Tue 6 OctGouda 08:13Partial coverage0 min—
Mon 5 OctGouda 08:12No data—
Fri 2 OctGouda 08:08No data—
Thu 1 OctGouda 08:08No data—
Wed 30 SeptGouda 08:12No data—
Tue 29 SeptGouda 08:09No data—
Mon 28 SeptGouda 08:10No data—
Fri 25 SeptGouda 08:09No data—
Thu 24 SeptGouda 08:08No data—
Wed 23 SeptGouda 08:09No data—
Tue 22 SeptGouda 08:10No data—
Mon 21 SeptGouda 08:08No data—