Train NS 2824 Utrecht Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Alexander at 09:49 +3 min

  1. Utrecht Centraal09:03
  2. Gouda09:21
  3. Rotterdam Alexander09:31
  4. Rotterdam Centraal09:40

Next service: tomorrow 09:03 from Utrecht Centraal · Fri 20 Nov

Next departure 09:03 tomorrow · Utrecht Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 5 full · 15 partial · 3 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 9 full · 20 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 9 Nov Max en route +3 min · last fix heading to Rotterdam Alexander +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 100% W n=6
  • 100% T n=5
  • 100% F n=4
  • 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, 29 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
09:03on time on time
09:21 / 09:22≈ on time ≈ on time
09:31≈ on time ≈ on time
09: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
Thu 19 NovRotterdam Alexander 09:49Partial coverage+3 min+4 min
Wed 18 NovRotterdam Alexander 09:44Partial coverage+1 min—
Tue 17 NovRotterdam Alexander 09:49Partial coverage+3 min+3 min
Mon 16 NovRotterdam Alexander 09:44Partial coverage+1 min—
Sun 15 NovRotterdam Alexander 09:44No data—
Sat 14 NovRotterdam Alexander 09:440 min—
Fri 13 NovRotterdam Alexander 09:440 min—
Thu 12 NovRotterdam Alexander 09:48Partial coverage+2 min+2 min
Wed 11 NovRotterdam Alexander 09:44Partial coverage0 min—
Tue 10 NovRotterdam Alexander 09:44Partial coverage+2 min+2 min
Mon 9 NovRotterdam Alexander 09:47Partial coverage+3 min+3 min
Fri 6 NovUtrecht Centraal 09:49No data—
Thu 5 NovRotterdam Alexander 09:48Partial coverage0 min—
Wed 4 NovRotterdam Alexander 09:44Partial coverage0 min—
Tue 3 NovRotterdam Alexander 09:49No data—
Mon 2 NovRotterdam Alexander 09:44Partial coverage0 min—
Sun 1 NovUtrecht Centraal 09:500 min—
Sat 31 OctRotterdam Alexander 09:460 min—
Fri 30 OctRotterdam Alexander 09:460 min—
Thu 29 OctRotterdam Alexander 09:47Partial coverage0 min—
Wed 28 OctRotterdam Alexander 09:48Partial coverage0 min—
Tue 27 OctRotterdam Alexander 09:48Partial coverage0 min—
Mon 26 OctRotterdam Alexander 09:50Partial coverage0 min—
Fri 16 OctRotterdam Alexander 09:450 min—
Thu 15 OctRotterdam Alexander 10:58No data—
Wed 14 OctRotterdam Alexander 09:51Partial coverage0 min—
Tue 13 OctRotterdam Alexander 09:52No data—
Mon 12 OctRotterdam Alexander 09:47Partial coverage0 min—
Sun 11 OctRotterdam Alexander 09:460 min—
Sat 10 OctRotterdam Alexander 09:46+1 min—