Train NS 2061 Rotterdam Centraal – Utrecht Centraal

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

✓ Today’s run finished

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

  1. Rotterdam Centraal16:35
  2. Rotterdam Alexander16:43
  3. Gouda16:53
  4. Utrecht Centraal17:12

Next service: tomorrow 16:35 from Rotterdam Centraal · Sat 14 Nov

Next departure 16:35 tomorrow · Rotterdam Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 9 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 3 full · 19 partial · 57 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

  • Tue 10 Nov Max en route +5 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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