Train NS 2065 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 17:35 → Utrecht Centraal 18:12 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 18:14 0 min

  1. Rotterdam Centraal17:35
  2. Rotterdam Alexander17:43
  3. Gouda17:53
  4. Utrecht Centraal18:12

Next service: tomorrow 17:35 from Rotterdam Centraal · Sat 7 Nov

Next departure 17:35 tomorrow · Rotterdam Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 1 full · 13 partial · 8 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 1 full · 16 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Mon 26 Oct Max en route +8 min · last fix heading to Gouda +8 min
  • Mon 5 Oct Max en route +7 min · last fix heading to Gouda +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 17 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:35on time on time
17:43— —
17:53 / 17:54— —
18: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 18:14Partial coverage0 min—
Thu 5 NovGouda 18:08Partial coverage0 min—
Wed 4 NovGouda 18:14Partial coverage0 min—
Tue 3 NovGouda 18:13No data—
Mon 2 NovGouda 18:14No data—
Sun 1 NovGouda 18:14Partial coverage0 min—
Sat 31 OctGouda 18:13Partial coverage0 min—
Fri 30 OctGouda 18:17No data—
Thu 29 OctGouda 18:15No data—
Wed 28 OctGouda 18:16Partial coverage0 min—
Tue 27 OctGouda 18:16No data—
Mon 26 OctGouda 18:30Partial coverage+8 min+8 min
Sat 17 OctGouda 18:180 min—
Fri 16 Oct— 17:41No data—
Thu 15 OctGouda 18:13No data—
Wed 14 OctGouda 18:14No data—
Tue 13 OctGouda 18:13Partial coverage0 min—
Mon 12 OctGouda 18:14Partial coverage0 min—
Sun 11 OctGouda 18:13Partial coverage0 min—
Sat 10 OctGouda 18:14Partial coverage0 min—
Fri 9 OctGouda 18:12Partial coverage0 min—
Thu 8 OctGouda 18:15Partial coverage0 min—
Wed 7 OctGouda 18:16Partial coverage+2 min+2 min
Tue 6 OctGouda 18:15Partial coverage+2 min+2 min
Mon 5 OctGouda 18:23Partial coverage+7 min+7 min
Sun 4 OctGouda 18:08No data—
Sat 3 OctGouda 18:09No data—
Fri 2 OctGouda 18:08No data—
Thu 1 OctGouda 18:08No data—
Wed 30 SeptGouda 18:08No data—