Train NS 1413 Utrecht Centraal – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Delft at 04:59 0 min

  1. Utrecht Centraal03:16
  2. Amsterdam Centraal03:44
  3. Schiphol Airport04:01
  4. Leiden Centraal04:21
  5. Den Haag HS04:37
  6. Delft04:45
  7. Rotterdam Centraal04:57

Next service: tomorrow 03:16 from Utrecht Centraal · Sat 14 Nov

Next departure 03:16 tomorrow · Utrecht Centraal
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 24 full · 1 partial · 1 no data
On-time · 90 days
100%
74/74 runs under 3 min
RT coverage: 73 full · 1 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 20% · 15
  • On time 80% · 59
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 74 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:16on time on time
03:44 / 03:46≈ on time ≈ on time
04:01 / 04:05≈ on time ≈ on time
04:21 / 04:23≈ on time ≈ on time
04:37 / 04:38≈ on time ≈ on time
04:45≈ on time ≈ on time
04:57on time on time

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
Fri 13 NovDelft 04:59Partial coverage0 min—
Wed 11 NovDelft 04:590 min—
Tue 10 NovDelft 04:590 min—
Mon 9 NovDen Haag HS 04:520 min—
Sun 8 NovDen Haag HS 04:520 min—
Sat 7 NovDen Haag HS 04:520 min—
Fri 6 NovDen Haag HS 06:240 min—
Wed 4 NovDelft 04:590 min—
Tue 3 NovDelft 04:590 min—
Mon 2 NovDelft 05:040 min—
Sun 1 NovDelft 05:000 min—
Sat 31 OctDelft 05:000 min—
Fri 30 OctDelft 05:000 min—
Wed 28 OctDelft 05:000 min—
Tue 27 OctDelft 05:000 min—
Mon 26 OctDelft 05:000 min—
Sun 25 OctDelft 05:01No data—
Sat 24 OctDelft 05:000 min—
Fri 23 OctDelft 05:030 min—
Thu 22 OctDelft 05:010 min—
Wed 21 OctDelft 05:200 min—
Tue 20 OctDelft 05:000 min—
Mon 19 OctDelft 04:590 min—
Sun 18 OctDelft 05:000 min—
Sat 17 OctDelft 04:590 min—
Fri 16 OctDelft 04:590 min—
Wed 14 OctDelft 04:590 min—
Tue 13 OctDelft 05:000 min—
Mon 12 OctDelft 05:000 min—
Sun 11 OctDen Haag HS 05:460 min—