Train NS 1406 Rotterdam Centraal – Utrecht Centraal

Rotterdam Centraal 01:00 → Utrecht Centraal 02:58 Daily 1 h 58 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 01:00 from Rotterdam Centraal · Sat 7 Nov

Next departure 01:00 today · Rotterdam Centraal
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 6 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 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=3
  • 100% S n=6

Stops and timetable

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

Last 90 days, 34 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
01:00on time on time
01:12≈ on time ≈ on time
01:19 / 01:34≈ on time ≈ on time
01:46 / 01:47≈ on time ≈ on time
02:02 / 02:03≈ on time ≈ on time
02:17 / 02:19≈ on time ≈ on time
02:58on 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 6 Nov— 03:290 min—
Thu 5 Nov— 02:590 min—
Wed 4 Nov— 02:490 min—
Mon 2 NovAmsterdam Centraal 02:370 min—
Sun 1 Nov— 02:560 min—
Fri 30 Oct— 03:030 min—
Thu 29 Oct— 01:530 min—
Wed 28 Oct— 02:540 min—
Tue 27 Oct— 02:510 min—
Mon 26 OctLeiden Centraal 03:240 min—
Sun 25 Oct— 02:520 min—
Sat 24 Oct— 02:540 min—
Fri 23 Oct— 02:590 min—
Thu 22 Oct— 03:420 min—
Wed 21 Oct— 03:130 min—
Tue 20 Oct— 02:520 min—
Mon 19 OctSchiphol Airport 02:500 min—
Sun 18 OctRotterdam Centraal 02:490 min—
Sat 17 Oct— 02:510 min—
Fri 16 Oct— 03:170 min—
Thu 15 Oct— 02:590 min—
Wed 14 Oct— 02:560 min—
Tue 13 Oct— 02:520 min—
Mon 12 OctSchiphol Airport 02:560 min—
Sun 11 Oct— 03:330 min—
Sat 10 Oct— 02:510 min—
Fri 9 Oct— 02:160 min—
Thu 8 Oct— 01:480 min—
Wed 7 Oct— 02:520 min—
Tue 6 Oct— 02:500 min—