Train NS 2877 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 20:50 from Rotterdam Centraal · Fri 6 Nov

Next departure 20:50 today · Rotterdam Centraal
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 12 full · 1 partial · 5 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 15 full · 1 partial · 16 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: +2 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 7 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 50% 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, 16 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
20:50on time on time
20:58≈ on time ≈ on time
21:08 / 21:09≈ on time ≈ +1 min
21:27on 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 5 Nov— 23:240 min—
Wed 4 Nov— 21:34+1 min—
Mon 2 Nov— 23:14+1 min+1 min
Sun 1 NovRotterdam Centraal 22:390 min—
Sat 31 OctGouda 21:34Partial coverage0 min—
Thu 29 Oct— 23:15+3 min+3 min
Wed 28 Oct— 23:16No data—
Tue 27 Oct— 21:35No data—
Mon 26 Oct— 21:34No data—
Fri 16 Oct— 21:500 min—
Thu 15 Oct— 21:520 min—
Wed 14 Oct— 21:34No data—
Tue 13 Oct— 22:07No data—
Mon 12 Oct— 21:530 min—
Sun 11 OctGouda 23:160 min—
Sat 10 OctGouda 23:160 min—
Fri 9 Oct— 23:16+2 min+2 min
Thu 8 Oct— 21:340 min—
Wed 7 Oct— 21:34+4 min+4 min
Tue 6 Oct— 21:170 min—
Mon 5 Oct— 23:160 min—
Sun 4 OctGouda 21:23No data—
Sat 3 OctGouda 21:25No data—
Sun 27 SeptGouda 21:31No data—
Sat 26 SeptGouda 21:22No data—
Sun 20 SeptGouda 21:25No data—
Sat 19 SeptGouda 21:23No data—
Sun 6 SeptGouda 21:24No data—
Sat 5 SeptGouda 21:24No data—
Sun 30 AugGouda 21:23No data—