Train NS 2870 Utrecht Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 21:14 +2 min

  1. Utrecht Centraal20:33
  2. Gouda20:51
  3. Rotterdam Alexander21:01
  4. Rotterdam Centraal21:10

Next service: tomorrow 20:33 from Utrecht Centraal · Fri 13 Nov

Next departure 20:33 tomorrow · Utrecht Centraal
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 11 full · 2 partial · 5 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 16 full · 4 partial · 16 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: +3 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 4 Nov Max en route +6 min · last fix heading to — +6 min
  • Fri 9 Oct Max en route +4 min · last fix heading to — +4 min
  • Wed 11 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 33% W n=3
  • 100% T n=3
  • 67% F n=3
  • 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, 20 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:33on time on time
20:51 / 20:52≈ on time ≈ +2 min
21:01≈ on time ≈ +3 min
21: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
Thu 12 Nov— 21:14+2 min+2 min
Wed 11 Nov— 21:15+3 min+3 min
Tue 10 Nov— 21:120 min—
Mon 9 Nov— 21:090 min—
Fri 6 Nov— 21:09+1 min—
Thu 5 Nov— 21:140 min—
Wed 4 Nov— 21:18+6 min+6 min
Mon 2 Nov— 20:590 min—
Sun 1 NovRotterdam Alexander 21:14Partial coverage+1 min—
Sat 31 OctRotterdam Alexander 21:29Partial coverage0 min—
Fri 30 Oct— 21:11No data—
Thu 29 Oct— 20:47+1 min+1 min
Wed 28 Oct— 21:17No data—
Tue 27 Oct— 21:12No data—
Mon 26 Oct— 21:110 min—
Fri 16 Oct— 21:120 min—
Thu 15 Oct— 21:11No data—
Wed 14 Oct— 21:12No data—
Tue 13 Oct— 21:12No data—
Mon 12 Oct— 21:130 min—
Sun 11 OctRotterdam Alexander 21:16Partial coverage0 min—
Sat 10 OctRotterdam Alexander 21:15Partial coverage+1 min—
Fri 9 Oct— 21:14+4 min+4 min
Wed 7 Oct— 21:110 min—
Tue 6 Oct— 20:470 min—
Mon 5 Oct— 21:12+1 min—
Sun 4 OctRotterdam Alexander 21:16No data—
Sat 3 OctRotterdam Alexander 21:21No data—
Sun 27 SeptRotterdam Alexander 21:16No data—
Sat 26 SeptRotterdam Alexander 21:23No data—