Train NS 2826 Utrecht Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Alexander at 10:17 +3 min

  1. Utrecht Centraal09:33
  2. Gouda09:51
  3. Rotterdam Alexander10:01
  4. Rotterdam Centraal10:10

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

Next departure 09:33 tomorrow · Utrecht Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 4 full · 12 partial · 7 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 8 full · 16 partial · 50 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: +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

  • Sat 10 Oct Max en route +4 min · last fix heading to Rotterdam Alexander +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=6
  • 100% F n=3
  • 67% 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, 24 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:33on time on time
09:51 / 09:52≈ on time ≈ +1 min
10:01≈ on time ≈ +1 min
10:10on time +2 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 10:17Partial coverage+3 min+3 min
Wed 18 NovRotterdam Alexander 10:14Partial coverage0 min—
Tue 17 NovRotterdam Alexander 10:14Partial coverage0 min—
Mon 16 NovRotterdam Alexander 10:17Partial coverage+1 min+1 min
Sun 15 NovRotterdam Alexander 10:14+1 min—
Sat 14 NovRotterdam Alexander 10:140 min—
Fri 13 NovRotterdam Alexander 10:140 min—
Thu 12 NovRotterdam Alexander 10:14Partial coverage0 min—
Wed 11 NovRotterdam Alexander 10:17Partial coverage+1 min+2 min
Tue 10 NovRotterdam Alexander 10:17Partial coverage+1 min+1 min
Mon 9 NovRotterdam Alexander 10:17Partial coverage+2 min+2 min
Fri 6 NovRotterdam Alexander 10:23No data—
Thu 5 NovRotterdam Alexander 10:14Partial coverage0 min—
Wed 4 NovRotterdam Alexander 10:14Partial coverage0 min—
Tue 3 NovRotterdam Alexander 10:28No data—
Mon 2 NovRotterdam Alexander 10:19Partial coverage0 min—
Sun 1 NovRotterdam Alexander 10:15No data—
Sat 31 OctRotterdam Alexander 10:160 min—
Fri 30 OctRotterdam Alexander 10:16No data—
Thu 29 OctRotterdam Alexander 10:17Partial coverage0 min—
Wed 28 OctRotterdam Alexander 10:16No data—
Tue 27 OctRotterdam Alexander 10:16No data—
Mon 26 OctRotterdam Alexander 10:16No data—
Fri 16 OctRotterdam Alexander 10:160 min—
Thu 15 OctRotterdam Alexander 10:16Partial coverage0 min—
Wed 14 OctRotterdam Alexander 10:16No data—
Tue 13 OctRotterdam Alexander 10:17No data—
Mon 12 OctRotterdam Alexander 10:16No data—
Sun 11 OctRotterdam Alexander 10:16+1 min+3 min
Sat 10 OctRotterdam Alexander 10:17+4 min+4 min