Train NS 2883 Rotterdam Centraal – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 22:20 from Rotterdam Centraal · Fri 6 Nov

Next departure 22:20 today · Rotterdam Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 2 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 13 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

  • Fri 9 Oct Max en route +4 min · last fix heading to — +4 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 95% · 18
  • 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=2
  • 100% 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, 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
22:20on time on time
22:28≈ on time ≈ on time
22:38 / 22:39≈ on time ≈ on time
22: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
Thu 5 Nov— 00:440 min—
Wed 4 Nov— 22:580 min—
Mon 2 Nov— 00:440 min+1 min
Sun 1 NovGouda 00:440 min—
Sat 31 OctGouda 00:450 min—
Fri 30 Oct— 23:060 min—
Thu 29 Oct— 00:580 min—
Wed 28 Oct— 00:450 min—
Tue 27 Oct— 00:500 min—
Mon 26 Oct— 00:470 min—
Fri 16 Oct— 23:040 min—
Thu 15 Oct— 23:39No data—
Tue 13 Oct— 23:20No data—
Mon 12 Oct— 23:29+1 min+4 min
Sun 11 OctGouda 00:450 min—
Sat 10 Oct— 23:05+2 min+2 min
Fri 9 Oct— 23:04+4 min+4 min
Thu 8 Oct— 23:040 min—
Wed 7 Oct— 00:450 min—
Tue 6 Oct— 00:450 min—
Mon 5 OctGouda 01:120 min+3 min
Sun 4 OctGouda 22:55No data—
Sat 3 OctGouda 22:51No data—
Sun 27 SeptGouda 22:53No data—
Sat 26 SeptGouda 22:52No data—
Sun 20 SeptGouda 22:58No data—
Sat 19 SeptGouda 22:53No data—
Sun 6 SeptGouda 22:53No data—
Sat 5 SeptGouda 22:52No data—
Sun 30 AugGouda 22:53No data—