Train NS 2876 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 22:03 → Rotterdam Centraal 22:40 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 22:03 from Utrecht Centraal · Fri 6 Nov

Next departure 22:03 today · Utrecht Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 2 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 13 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: +2 min

Last 30 days

Arrival delay at Rotterdam 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 +8 min · last fix heading to — +8 min
  • Mon 2 Nov Max en route +4 min · last fix heading to — +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +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

  • 50% M n=4
  • 100% T n=3
  • 75% W n=4
  • 100% T n=2
  • 100% F n=1
  • 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, 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
22:03on time on time
22:21 / 22:22≈ on time ≈ +2 min
22:31≈ on time ≈ +3 min
22:40on 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
Thu 5 Nov— 22:390 min—
Wed 4 Nov— 22:390 min—
Mon 2 Nov— 22:39+4 min+4 min
Sun 1 NovRotterdam Alexander 22:440 min—
Sat 31 OctRotterdam Alexander 22:480 min—
Fri 30 Oct— 22:41No data—
Thu 29 Oct— 22:41+2 min+2 min
Wed 28 Oct— 22:300 min—
Tue 27 Oct— 22:420 min—
Mon 26 Oct— 22:410 min—
Thu 15 Oct— 22:43No data—
Wed 14 Oct— 22:410 min—
Tue 13 Oct— 22:470 min—
Mon 12 Oct— 22:410 min—
Sun 11 OctRotterdam Alexander 22:460 min—
Sat 10 OctUtrecht Centraal 22:170 min—
Fri 9 Oct— 22:47+2 min+3 min
Wed 7 Oct— 22:46+8 min+8 min
Tue 6 Oct— 22:300 min—
Mon 5 Oct— 22:41+3 min+3 min
Sun 4 OctRotterdam Alexander 22:46No data—
Sat 3 OctRotterdam Alexander 22:45No data—
Sun 27 SeptRotterdam Alexander 22:46No data—
Sat 26 SeptRotterdam Alexander 22:46No data—
Sun 20 SeptRotterdam Alexander 22:46No data—
Sat 19 SeptRotterdam Alexander 22:45No data—
Sun 6 SeptRotterdam Alexander 22:47No data—
Sat 5 SeptRotterdam Alexander 22:45No data—
Sun 30 AugRotterdam Alexander 22:47No data—
Sat 29 AugRotterdam Alexander 22:45No data—