Train NS 2875 Rotterdam Centraal – Utrecht Centraal

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

✓ Today’s run finished

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

  1. Rotterdam Centraal20:20
  2. Rotterdam Alexander20:28
  3. Gouda20:38
  4. Utrecht Centraal20:57

Next service: Monday 20:20 from Rotterdam Centraal · Mon 9 Nov

Next departure 20:20 Monday · Rotterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 3 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 19 full · 1 partial · 14 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

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 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 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 50% W n=2
  • 100% T n=3
  • 100% 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:20on time on time
20:28≈ on time ≈ on time
20:38 / 20:39≈ on time ≈ on time
20:57on 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
Fri 6 Nov— 20:580 min—
Thu 5 Nov— 20:590 min—
Wed 4 Nov— 21:04+5 min+5 min
Tue 3 Nov— 20:580 min—
Mon 2 Nov— 20:590 min—
Sun 1 NovGouda 20:59Partial coverage+2 min+2 min
Sat 31 OctGouda 20:530 min—
Thu 29 Oct— 20:58+1 min—
Wed 28 Oct— 20:59No data—
Tue 27 Oct— 20:590 min—
Mon 26 Oct— 20:580 min—
Fri 16 Oct— 20:590 min—
Thu 15 Oct— 21:01No data—
Wed 14 Oct— 20:58No data—
Tue 13 Oct— 20:590 min—
Mon 12 Oct— 20:590 min—
Sun 11 OctGouda 20:580 min—
Sat 10 OctGouda 20:590 min—
Fri 9 Oct— 20:590 min—
Thu 8 Oct— 21:450 min—
Wed 7 Oct— 20:580 min—
Tue 6 Oct— 20:59+1 min+2 min
Mon 5 Oct— 20:580 min—
Sun 4 OctGouda 20:54No data—
Sat 3 OctGouda 20:56No data—
Sun 27 SeptGouda 20:54No data—
Sat 26 SeptGouda 20:52No data—
Sun 20 SeptGouda 20:53No data—
Sat 19 SeptGouda 20:53No data—
Sun 6 SeptGouda 20:52No data—