Train NS 2884 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 00:03 → Rotterdam Centraal 00:40 Daily 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:39 +1 min

  1. Utrecht Centraal00:03
  2. Gouda00:21
  3. Rotterdam Alexander00:31
  4. Rotterdam Centraal00:40

Next service: Monday 00:03 from Utrecht Centraal · Mon 9 Nov

Next departure 00:03 Monday · Utrecht Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 1 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 8 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 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

  • Tue 13 Oct Max en route +5 min · last fix heading to — +5 min

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 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 50% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 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
00:03on time on time
00:21 / 00:22≈ on time ≈ on time
00:31≈ on time ≈ +1 min
00:40on 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
Sat 7 Nov— 00:39+1 min+2 min
Fri 6 Nov— 00:390 min—
Thu 5 Nov— 00:420 min—
Wed 4 Nov— 00:390 min—
Tue 3 Nov— 00:390 min—
Sun 1 NovRotterdam Alexander 00:44Partial coverage0 min—
Sat 31 Oct— 00:410 min—
Fri 30 Oct— 00:410 min—
Wed 28 Oct— 00:42No data—
Sat 17 Oct— 00:410 min—
Thu 15 Oct— 00:410 min—
Wed 14 Oct— 06:070 min—
Tue 13 Oct— 00:41+5 min+5 min
Sun 11 OctRotterdam Alexander 00:460 min—
Fri 9 Oct— 00:410 min—
Thu 8 Oct— 00:41No data—
Wed 7 Oct— 00:410 min—
Sun 4 OctRotterdam Alexander 00:45No data—
Sat 3 OctRotterdam Alexander 00:45No data—
Sun 27 SeptRotterdam Alexander 00:47No data—
Sun 20 SeptRotterdam Alexander 00:46No data—
Sun 6 SeptRotterdam Alexander 00:45No data—
Sun 30 AugRotterdam Alexander 00:46No data—