Train NS 2874 Utrecht Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 22:09 0 min

  1. Utrecht Centraal21:33
  2. Gouda21:51
  3. Rotterdam Alexander22:01
  4. Rotterdam Centraal22:10

Next service: tomorrow 21:33 from Utrecht Centraal · Thu 19 Nov

Next departure 21:33 tomorrow · Utrecht Centraal
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 13 full · 0 partial · 2 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 14 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Tue 17 Nov Max en route +9 min · last fix heading to — +9 min
  • Fri 6 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 50% T n=2
  • 100% W n=4
  • 100% T n=2
  • 50% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 stops).

Last 90 days, 19 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:33on time on time
21:51 / 21:52≈ on time ≈ +3 min
22:01≈ +1 min ≈ +3 min
22:10+1 min +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 18 Nov— 22:090 min—
Tue 17 Nov— 22:17+9 min+9 min
Mon 16 NovUtrecht Centraal 22:12+1 min—
Sun 15 NovRotterdam Alexander 22:17+2 min+2 min
Sat 14 NovRotterdam Alexander 22:14+1 min+1 min
Thu 12 Nov— 22:14+2 min+2 min
Wed 11 Nov— 22:100 min—
Tue 10 Nov— 22:09No data—
Fri 6 Nov— 22:17+5 min+5 min
Wed 4 Nov— 22:12+2 min+2 min
Mon 2 Nov— 22:090 min—
Sun 1 NovRotterdam Alexander 22:14+1 min+1 min
Sat 31 OctRotterdam Alexander 22:15No data—
Tue 27 Oct— 22:120 min—
Mon 26 Oct— 22:110 min—
Thu 15 Oct— 22:11No data—
Wed 14 Oct— 22:110 min—
Tue 13 Oct— 22:11No data—
Mon 12 Oct— 22:110 min—
Sun 11 OctRotterdam Alexander 22:160 min—
Sat 10 OctRotterdam Alexander 22:15+2 min+2 min
Fri 9 Oct— 22:17+3 min+3 min
Thu 8 Oct— 22:12+3 min+3 min
Sun 4 OctRotterdam Alexander 22:17No data—
Sat 3 OctRotterdam Alexander 22:16No data—
Sun 27 SeptRotterdam Alexander 22:18No data—
Sat 26 SeptRotterdam Alexander 22:17No data—
Sun 20 SeptRotterdam Alexander 22:16No data—
Sat 19 SeptRotterdam Alexander 22:15No data—
Sun 6 SeptRotterdam Alexander 22:21No data—