Train NS 2878 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 22:33 → Rotterdam Centraal 23:10 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 22:33 from Utrecht Centraal · Fri 13 Nov

Next departure 22:33 today · Utrecht Centraal
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 3 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Wed 7 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 67% W n=3
  • 100% T n=2
  • 75% F n=4
  • 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, 14 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:33on time on time
22:51 / 22:52≈ on time ≈ +2 min
23:01≈ on time ≈ +3 min
23:10on time +4 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 11 Nov— 23:090 min—
Fri 6 Nov— 23:17+3 min+3 min
Tue 3 Nov— 23:09No data—
Sun 1 NovRotterdam Alexander 23:140 min—
Sat 31 OctRotterdam Alexander 23:150 min—
Fri 30 Oct— 23:110 min—
Thu 29 Oct— 23:110 min—
Wed 28 Oct— 23:110 min—
Tue 27 Oct— 23:11No data—
Mon 26 Oct— 23:11No data—
Fri 16 Oct— 23:11+2 min+2 min
Tue 13 Oct— 23:12No data—
Sun 11 OctRotterdam Alexander 23:160 min—
Sat 10 Oct— 23:120 min—
Fri 9 Oct— 23:17+5 min+5 min
Thu 8 Oct— 23:110 min—
Wed 7 Oct— 23:18+5 min+6 min
Tue 6 Oct— 22:470 min—
Sun 4 OctRotterdam Alexander 23:16No data—
Sat 3 OctRotterdam Alexander 23:15No data—
Sun 27 SeptRotterdam Alexander 23:17No data—
Sat 26 SeptRotterdam Alexander 23:16No data—
Sun 20 SeptRotterdam Alexander 23:32No data—
Sat 19 SeptRotterdam Alexander 23:08No data—
Sun 6 SeptRotterdam Alexander 23:16No data—
Sat 5 SeptGouda 23:06No data—
Sun 30 AugRotterdam Alexander 23:18No data—
Sat 29 AugUtrecht Centraal 22:47No data—