Train NS 2063 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 17:05 → Utrecht Centraal 17:42 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 17:05 from Rotterdam Centraal · Sat 14 Nov

Next departure 17:05 today · Rotterdam Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 4 full · 11 partial · 6 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 4 full · 19 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Wed 11 Nov Max en route +13 min · last fix heading to Gouda +13 min
  • Mon 26 Oct Max en route +6 min · last fix heading to Gouda +6 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Gouda +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 75% W n=4
  • 50% T n=2
  • 100% F n=5
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 23 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
17:05on time on time
17:13— —
17:23 / 17:24— —
17:42— —

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 17:43Partial coverage0 min+1 min
Thu 12 NovRotterdam Centraal 17:44Partial coverageNo data—
Wed 11 NovGouda 18:08Partial coverage+13 min+13 min
Tue 10 NovGouda 17:44Partial coverage0 min—
Mon 9 NovGouda 17:44Partial coverage0 min—
Sun 8 NovGouda 17:440 min—
Sat 7 NovGouda 17:440 min+1 min
Fri 6 NovGouda 17:44Partial coverage0 min—
Thu 5 NovGouda 17:44Partial coverage0 min—
Wed 4 NovGouda 17:44Partial coverage0 min—
Tue 3 NovGouda 17:38No data—
Mon 2 NovGouda 17:38No data—
Sun 1 NovGouda 17:38No data—
Sat 31 OctGouda 17:43Partial coverage0 min—
Fri 30 OctGouda 17:43Partial coverage0 min—
Thu 29 OctGouda 18:02No data—
Wed 28 OctGouda 17:43Partial coverage0 min—
Tue 27 OctGouda 17:44No data—
Mon 26 OctGouda 17:53Partial coverage+6 min+6 min
Sat 17 OctGouda 17:430 min—
Fri 16 Oct— 17:430 min—
Thu 15 OctGouda 17:45No data—
Wed 14 OctGouda 17:44No data—
Tue 13 OctGouda 17:44No data—
Mon 12 OctGouda 17:50Partial coverage0 min—
Sun 11 OctGouda 17:43Partial coverage0 min—
Sat 10 OctGouda 17:43Partial coverage0 min—
Fri 9 OctGouda 17:45Partial coverage+1 min+1 min
Thu 8 OctGouda 17:48Partial coverage+5 min+5 min
Wed 7 OctGouda 17:46Partial coverage+2 min+2 min