Train NS 2873 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 19:50 → Utrecht Centraal 20:27 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 20:29 0 min

  1. Rotterdam Centraal19:50
  2. Rotterdam Alexander19:58
  3. Gouda20:08
  4. Utrecht Centraal20:27

Next service: tomorrow 19:50 from Rotterdam Centraal · Fri 6 Nov

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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • — T n=0
  • 100% W n=3
  • 100% T n=3
  • 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, 15 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
19:50on time on time
19:58≈ on time ≈ on time
20:08 / 20:09≈ on time ≈ on time
20:27on time +1 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— 20:290 min—
Wed 4 Nov— 20:29+3 min+3 min
Tue 3 Nov— 20:29No data—
Mon 2 Nov— 20:17No data—
Sun 1 NovGouda 20:29Partial coverage0 min—
Sat 31 OctGouda 20:36Partial coverage+2 min+2 min
Fri 30 Oct— 20:30No data—
Thu 29 Oct— 20:240 min—
Wed 28 Oct— 20:280 min—
Tue 27 Oct— 20:30No data—
Mon 26 Oct— 20:280 min—
Fri 16 OctRotterdam Centraal 20:30Partial coverage0 min—
Thu 15 Oct— 20:30No data—
Wed 14 Oct— 20:28No data—
Tue 13 Oct— 20:29No data—
Mon 12 Oct— 20:290 min—
Sun 11 OctGouda 20:28Partial coverage0 min—
Sat 10 OctGouda 20:29Partial coverage0 min—
Fri 9 Oct— 20:290 min—
Thu 8 Oct— 21:170 min—
Wed 7 Oct— 20:330 min—
Tue 6 Oct— 20:23No data—
Mon 5 Oct— 20:30+1 min—
Sun 4 OctGouda 20:23No data—
Sat 3 OctGouda 20:32No data—
Sun 27 SeptGouda 20:22No data—
Sat 26 SeptGouda 20:22No data—
Sun 20 SeptGouda 20:23No data—
Sat 19 SeptGouda 20:23No data—
Sun 6 SeptGouda 20:23No data—