Train NS 2871 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 19:20 from Rotterdam Centraal · Thu 5 Nov

Next departure 19:20 today · Rotterdam Centraal
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 5 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 19 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: +5 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

  • Thu 29 Oct Max en route +10 min · last fix heading to — +10 min
  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 67% T n=3
  • 0% F n=1
  • 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, 16 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:20on time on time
19:28≈ on time ≈ +1 min
19:38 / 19:39≈ on time ≈ +2 min
19:57on 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 4 Nov— 19:590 min—
Mon 2 Nov— 19:590 min—
Sun 1 NovGouda 19:590 min—
Sat 31 OctGouda 19:580 min—
Fri 30 Oct— 20:00No data—
Thu 29 Oct— 20:03+10 min+10 min
Wed 28 Oct— 19:590 min—
Tue 27 Oct— 19:580 min—
Mon 26 Oct— 19:58No data—
Fri 16 OctGouda 19:58No data—
Thu 15 Oct— 19:590 min—
Wed 14 OctGouda 19:59No data—
Tue 13 Oct— 19:59No data—
Mon 12 Oct— 19:580 min—
Sun 11 OctGouda 19:580 min—
Sat 10 OctGouda 19:59+2 min+2 min
Fri 9 Oct— 20:02+6 min+6 min
Thu 8 Oct— 20:080 min—
Wed 7 Oct— 19:580 min—
Tue 6 Oct— 19:580 min—
Mon 5 Oct— 19:580 min—
Sun 4 OctGouda 19:53No data—
Sat 3 OctGouda 19:53No data—
Sun 27 SeptGouda 19:53No data—
Sat 26 SeptGouda 19:57No data—
Sun 20 SeptGouda 19:53No data—
Sat 19 SeptGouda 19:53No data—
Sun 6 SeptGouda 19:53No data—
Sat 5 SeptGouda 19:53No data—
Sun 30 AugGouda 19:53No data—