Train NS 2879 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:20 from Rotterdam Centraal · Thu 5 Nov

Next departure 21:20 today · Rotterdam Centraal
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 5 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 17 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

  • Tue 6 Oct Max en route +8 min · last fix heading to — +7 min
  • Mon 5 Oct Max en route +7 min · last fix heading to — +5 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

  • 75% M n=4
  • 67% T n=3
  • 100% W n=2
  • 100% T n=2
  • 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
21:20on time on time
21:28≈ on time ≈ +1 min
21:38 / 21:39≈ on time ≈ +1 min
21:57on time +3 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
Wed 4 Nov— 22:040 min—
Tue 3 Nov— 21:590 min—
Mon 2 Nov— 22:040 min—
Sun 1 NovGouda 21:530 min—
Sat 31 OctGouda 21:580 min—
Fri 30 Oct— 23:47No data—
Thu 29 Oct— 23:48+1 min+1 min
Wed 28 Oct— 23:45No data—
Tue 27 Oct— 21:590 min—
Mon 26 Oct— 23:450 min—
Fri 16 Oct— 22:20+1 min+2 min
Thu 15 Oct— 22:22No data—
Wed 14 Oct— 22:04No data—
Tue 13 Oct— 22:21No data—
Mon 12 Oct— 22:110 min—
Sun 11 OctGouda 22:040 min—
Sat 10 OctGouda 23:460 min—
Fri 9 Oct— 23:450 min—
Thu 8 Oct— 00:140 min—
Wed 7 Oct— 22:040 min—
Tue 6 Oct— 22:13+7 min+8 min
Mon 5 Oct— 22:04+5 min+7 min
Sun 4 OctGouda 21:57No data—
Sat 3 OctGouda 21:54No data—
Sun 27 SeptGouda 21:52No data—
Sat 26 SeptGouda 21:53No data—
Sun 20 SeptGouda 21:54No data—
Sat 19 SeptGouda 21:53No data—
Sun 6 SeptGouda 21:52No data—
Sat 5 SeptGouda 21:53No data—