Train NS 2023 Rotterdam Centraal – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 07:44 0 min

  1. Rotterdam Centraal07:05
  2. Rotterdam Alexander07:13
  3. Gouda07:23
  4. Utrecht Centraal07:42

Next service: Monday 07:05 from Rotterdam Centraal · Mon 16 Nov

Next departure 07:05 Monday · Rotterdam Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 3 full · 12 partial · 2 no data
On-time · 90 days
91%
40/44 runs under 3 min
RT coverage: 25 full · 19 partial · 15 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

  • Fri 18 Sept Max en route +23 min · last fix heading to Rotterdam Centraal +14 min
  • Fri 11 Sept Max en route +8 min · last fix heading to Rotterdam Centraal +4 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Gouda +4 min
  • Mon 26 Oct Max en route +3 min · last fix heading to Gouda +3 min

Distribution · 90 days

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

  • Early 30% · 13
  • On time 61% · 27
  • 3–10 min 7% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 100% T n=10
  • 100% W n=8
  • 100% T n=9
  • 78% 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, 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
07:05on time on time
07:13≈ on time ≈ +1 min
07:23 / 07:24≈ on time ≈ +2 min
07:421 min early +4 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 NovGouda 07:44Partial coverage0 min—
Thu 12 NovGouda 07:44Partial coverage+1 min+2 min
Wed 11 NovGouda 07:43Partial coverage0 min—
Tue 10 NovGouda 07:44Partial coverage+2 min+3 min
Mon 9 NovGouda 07:44+4 min+6 min
Fri 6 NovGouda 07:44No data—
Thu 5 NovGouda 07:39Partial coverage0 min—
Wed 4 NovGouda 07:38Partial coverage0 min—
Tue 3 NovGouda 08:190 min—
Mon 2 NovGouda 07:44No data—
Fri 30 OctGouda 07:43Partial coverage0 min—
Thu 29 OctGouda 07:44Partial coverage+1 min+1 min
Wed 28 OctGouda 07:44Partial coverage+1 min+1 min
Tue 27 OctGouda 07:46Partial coverage0 min—
Mon 26 OctGouda 07:45+3 min+3 min
Fri 16 OctGouda 07:43Partial coverage0 min—
Thu 15 OctGouda 07:44Partial coverage0 min—
Wed 14 OctGouda 07:44Partial coverage0 min—
Tue 13 OctGouda 07:45Partial coverage0 min—
Mon 12 OctGouda 07:43Partial coverage0 min—
Fri 9 OctGouda 07:48Partial coverage+1 min+2 min
Thu 8 OctGouda 07:46Partial coverage+1 min+1 min
Wed 7 OctGouda 07:43Partial coverage0 min—
Tue 6 OctGouda 07:44Partial coverage+1 min+1 min
Mon 5 OctGouda 07:39No data—
Fri 2 OctRotterdam Centraal 01:040 min+10 min
Thu 1 OctRotterdam Centraal 19:38−3 min—
Wed 30 SeptRotterdam Centraal 19:03+2 min+6 min
Tue 29 SeptRotterdam Alexander 18:48−3 min+5 min
Mon 28 SeptRotterdam Alexander 23:19−1 min+2 min