Train NS 2829 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 08:50 → Utrecht Centraal 09:27 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 09:32 +2 min

  1. Rotterdam Centraal08:50
  2. Rotterdam Alexander08:58
  3. Gouda09:08
  4. Utrecht Centraal09:27

Next service: tomorrow 08:50 from Rotterdam Centraal · Tue 10 Nov

Next departure 08:50 tomorrow · Rotterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 5 full · 7 partial · 7 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 7 full · 10 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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 100% · 17
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=4
  • 100% F n=2
  • 100% S n=2
  • 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
08:50on time on time
08:58≈ on time ≈ on time
09:08 / 09:09≈ on time ≈ on time
09:27on time on time

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
Mon 9 NovGouda 09:32Partial coverage+2 min+2 min
Fri 6 NovGouda 09:28No data—
Thu 5 NovGouda 09:29Partial coverage0 min—
Wed 4 NovGouda 09:29Partial coverage0 min—
Tue 3 NovGouda 09:57No data—
Mon 2 NovRotterdam Centraal 09:29Partial coverage0 min—
Sun 1 NovGouda 09:54+1 min—
Sat 31 OctGouda 09:280 min—
Fri 30 OctGouda 09:28No data—
Thu 29 OctGouda 09:30Partial coverage0 min—
Wed 28 OctGouda 09:31No data—
Tue 27 OctGouda 09:31Partial coverage0 min—
Mon 26 OctGouda 09:30No data—
Fri 16 OctGouda 09:290 min—
Thu 15 OctGouda 10:580 min—
Wed 14 OctGouda 09:28No data—
Tue 13 OctGouda 09:30No data—
Mon 12 OctGouda 09:29Partial coverage0 min—
Sun 11 OctGouda 11:150 min—
Sat 10 OctGouda 09:280 min—
Fri 9 OctGouda 09:280 min—
Thu 8 OctGouda 09:29Partial coverage+2 min+3 min
Wed 7 OctGouda 09:29Partial coverage0 min—
Tue 6 OctGouda 09:30Partial coverage+1 min+1 min
Mon 5 OctGouda 09:32No data—
Sun 4 OctGouda 09:23No data—
Sat 3 OctGouda 09:24No data—
Fri 2 OctGouda 09:23No data—
Thu 1 OctGouda 09:24No data—
Wed 30 SeptGouda 09:23No data—