Train NS 1414 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 03:02 → Utrecht Centraal 04:48 Mon, Tue, Thu, Fri, Sat, Sun 1 h 46 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: tomorrow 03:02 from Rotterdam Centraal · Fri 6 Nov

Next departure 03:02 tomorrow · Rotterdam Centraal
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 20 full · 5 partial · 1 no data
On-time · 90 days
100%
72/72 runs under 3 min
RT coverage: 67 full · 5 partial · 6 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: 0 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

Distribution · 90 days

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

  • Early 25% · 18
  • On time 75% · 54
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=13
  • 100% W n=12
  • 100% T n=3
  • 100% F n=9
  • 100% S n=12
  • 100% S n=11

Stops and timetable

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

Last 90 days, 72 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
03:02on time on time
03:14≈ on time ≈ on time
03:21 / 03:22≈ on time ≈ on time
03:36 / 03:45≈ on time ≈ on time
04:17 / 04:19≈ on time ≈ on time
04:29 / 04:30≈ on time ≈ on time
04:48on 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
Wed 4 NovAmsterdam Bijlmer ArenA 04:49Partial coverage0 min—
Tue 3 NovSchiphol Airport 04:49Partial coverage0 min—
Mon 2 NovAmsterdam Centraal 04:370 min—
Sun 1 NovAmsterdam Centraal 04:330 min—
Sat 31 OctAmsterdam Centraal 04:360 min—
Fri 30 OctRotterdam Centraal 04:590 min—
Wed 28 OctAmsterdam Bijlmer ArenA 04:500 min—
Tue 27 OctSchiphol Airport 04:490 min—
Mon 26 OctSchiphol Airport 04:490 min—
Sun 25 OctAmsterdam Bijlmer ArenA 04:51No data—
Sat 24 OctSchiphol Airport 04:50+1 min+1 min
Fri 23 OctSchiphol Airport 04:590 min—
Thu 22 OctSchiphol Airport 05:040 min—
Wed 21 OctAmsterdam Bijlmer ArenA 05:270 min—
Tue 20 OctSchiphol Airport 04:50Partial coverage0 min—
Mon 19 OctSchiphol Airport 04:500 min—
Sun 18 OctSchiphol Airport 04:540 min—
Sat 17 OctRotterdam Centraal 04:500 min—
Fri 16 OctSchiphol Airport 05:100 min—
Wed 14 OctAmsterdam Bijlmer ArenA 04:49Partial coverage0 min—
Tue 13 OctSchiphol Airport 04:52Partial coverage0 min—
Mon 12 OctSchiphol Airport 04:490 min—
Sun 11 OctGouda 05:340 min—
Sat 10 OctSchiphol Airport 04:490 min—
Fri 9 OctAmsterdam Centraal 04:370 min—
Wed 7 OctAmsterdam Bijlmer ArenA 04:490 min—
Tue 6 OctSchiphol Airport 04:490 min—
Mon 5 OctDen Haag HS 12:20−3 min+3 min
Sun 4 OctDen Haag HS 00:120 min—
Sat 3 OctRotterdam Centraal 20:190 min+2 min