Train NS 2016 Utrecht Centraal – Rotterdam Centraal

Utrecht Centraal 07:18 → Rotterdam Centraal 07:55 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November +2 min

Next service: today 07:18 from Utrecht Centraal · Tue 10 Nov

Next departure 07:18 today · Utrecht Centraal
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 3 no data
On-time · 90 days
95%
39/41 runs under 3 min
RT coverage: 30 full · 11 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 1 Oct Max en route +7 min · last fix heading to Rotterdam Alexander +3 min
  • Tue 8 Sept Max en route +6 min · last fix heading to Rotterdam Alexander +3 min

Distribution · 90 days

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

  • Early 22% · 9
  • On time 73% · 30
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 86% T n=7
  • 100% W n=8
  • 89% T n=9
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 stops).

Last 90 days, 41 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
07:18on time on time
07:36 / 07:37≈ on time ≈ +1 min
07:46≈ on time ≈ +2 min
07:55on time +3 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
Mon 9 NovRotterdam Alexander 08:03Partial coverage+2 min+3 min
Fri 6 NovRotterdam Alexander 07:59No data—
Thu 5 NovRotterdam Alexander 07:59Partial coverage0 min—
Wed 4 NovRotterdam Alexander 08:03+2 min+2 min
Tue 3 NovRotterdam Alexander 08:19No data—
Mon 2 NovRotterdam Alexander 08:02Partial coverage0 min—
Fri 30 OctRotterdam Alexander 08:01Partial coverage0 min—
Thu 29 OctRotterdam Alexander 08:08Partial coverage0 min—
Wed 28 OctRotterdam Alexander 08:06+2 min+3 min
Tue 27 OctRotterdam Alexander 08:120 min—
Mon 26 OctRotterdam Alexander 08:02Partial coverage+1 min+1 min
Fri 16 OctRotterdam Alexander 08:02Partial coverage0 min—
Thu 15 OctRotterdam Alexander 08:05Partial coverage0 min—
Wed 14 OctRotterdam Alexander 08:330 min—
Tue 13 OctUtrecht Centraal 08:25No data—
Mon 12 OctRotterdam Alexander 08:01Partial coverage0 min—
Fri 9 OctRotterdam Alexander 08:01Partial coverage+1 min—
Thu 8 OctRotterdam Alexander 08:03Partial coverage+2 min+3 min
Wed 7 OctRotterdam Alexander 08:01+1 min—
Tue 6 OctRotterdam Alexander 08:01+1 min—
Mon 5 OctRotterdam Alexander 08:05No data—
Fri 2 OctRotterdam Alexander 18:02+2 min+10 min
Thu 1 OctRotterdam Alexander 18:24+3 min+7 min
Wed 30 SeptRotterdam Alexander 00:54−2 min+3 min
Tue 29 SeptRotterdam Alexander 17:20+3 min+25 min
Mon 28 SeptRotterdam Alexander 17:300 min+3 min
Fri 25 SeptRotterdam Alexander 00:30+3 min+3 min
Thu 24 SeptRotterdam Alexander 00:24−5 min+10 min
Wed 23 SeptRotterdam Alexander 01:23+3 min+7 min
Tue 22 SeptRotterdam Alexander 00:14−6 min+4 min