Train NS 2835 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 10:20 → Utrecht Centraal 10:57 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 10:59 0 min

  1. Rotterdam Centraal10:20
  2. Rotterdam Alexander10:28
  3. Gouda10:38
  4. Utrecht Centraal10:57

Next service: tomorrow 10:20 from Rotterdam Centraal · Fri 13 Nov

Next departure 10:20 tomorrow · Rotterdam Centraal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 2 full · 10 partial · 7 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 6 full · 12 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Thu 8 Oct Max en route +9 min · last fix heading to Gouda +9 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Gouda +4 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Gouda +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 15
  • 3–10 min 17% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
10:20on time on time
10:28≈ on time ≈ on time
10:38 / 10:39≈ on time ≈ +1 min
10:57on time +2 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
Thu 12 NovGouda 10:59Partial coverage0 min—
Wed 11 NovGouda 10:59Partial coverage0 min—
Tue 10 NovGouda 10:58Partial coverage0 min+1 min
Mon 9 NovGouda 10:59Partial coverage0 min—
Fri 6 NovGouda 10:59No data—
Thu 5 NovGouda 11:09Partial coverage0 min—
Wed 4 NovGouda 10:58Partial coverage0 min—
Tue 3 NovGouda 11:04No data—
Mon 2 NovRotterdam Centraal 10:59Partial coverage0 min—
Sun 1 NovGouda 11:26+3 min+3 min
Sat 31 OctGouda 10:530 min—
Fri 30 OctGouda 10:58No data—
Thu 29 OctGouda 10:58Partial coverage0 min—
Wed 28 OctGouda 10:58Partial coverage0 min—
Tue 27 OctGouda 10:59No data—
Mon 26 OctGouda 10:58No data—
Fri 16 OctGouda 10:58No data—
Thu 15 OctGouda 11:00Partial coverage0 min—
Wed 14 OctGouda 10:58No data—
Tue 13 OctGouda 11:00No data—
Mon 12 OctGouda 10:59No data—
Sun 11 OctGouda 12:450 min—
Sat 10 OctGouda 11:00+1 min+1 min
Fri 9 OctGouda 10:590 min—
Thu 8 OctGouda 11:15Partial coverage+9 min+9 min
Wed 7 OctRotterdam Centraal 12:010 min—
Tue 6 OctGouda 11:00Partial coverage+4 min+5 min
Mon 5 OctGouda 10:55No data—
Sun 4 OctGouda 10:53No data—
Sat 3 OctGouda 10:53No data—