Train NS 2014 Utrecht Centraal – Rotterdam Centraal
✓ Today’s run finished
Today, last fix heading to Rotterdam Alexander at 07:29 0 min
- Utrecht Centraal06:48
- Gouda07:06
- Rotterdam Alexander07:16
- Rotterdam Centraal07:25
Next service: tomorrow 06:48 from Utrecht Centraal · Thu 12 Nov
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 29 Oct Max en route +16 min · last fix heading to Rotterdam Alexander +16 min
- Tue 13 Oct Max en route +4 min · last fix heading to Rotterdam Alexander +4 min
- Thu 15 Oct Max en route +3 min · last fix heading to Rotterdam Alexander +3 min
Distribution · 90 days
43 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 19% · 8
- On time 74% · 32
- 3–10 min 5% · 2
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 89% T n=9
- 100% W n=8
- 75% T n=8
- 100% F n=9
- 100% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 43 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:48 | on time | on time | |
| 07:06 / 07:07 | ≈ on time | ≈ +1 min | |
| 07:16 | ≈ on time | ≈ +1 min | |
| 07:25 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 11 Nov | Rotterdam Alexander 07:29Partial coverage | 0 min | — |
| Tue 10 Nov | Rotterdam Alexander 07:32 | +2 min | +2 min |
| Mon 9 Nov | Rotterdam Alexander 07:29 | 0 min | — |
| Fri 6 Nov | Rotterdam Alexander 07:30 | No data | — |
| Thu 5 Nov | Rotterdam Alexander 07:29 | No data | — |
| Wed 4 Nov | Rotterdam Alexander 07:29Partial coverage | 0 min | — |
| Tue 3 Nov | Rotterdam Alexander 07:29 | 0 min | — |
| Mon 2 Nov | Rotterdam Alexander 07:32 | No data | — |
| Fri 30 Oct | Rotterdam Alexander 07:31 | +1 min | — |
| Thu 29 Oct | Rotterdam Alexander 07:46Partial coverage | +16 min | +16 min |
| Wed 28 Oct | Rotterdam Alexander 07:31Partial coverage | 0 min | — |
| Tue 27 Oct | Rotterdam Alexander 07:33 | +1 min | +1 min |
| Mon 26 Oct | Rotterdam Alexander 07:32 | +1 min | +2 min |
| Fri 16 Oct | Rotterdam Alexander 07:31 | 0 min | — |
| Thu 15 Oct | Rotterdam Alexander 07:35Partial coverage | +3 min | +3 min |
| Wed 14 Oct | Rotterdam Alexander 07:31Partial coverage | +1 min | — |
| Tue 13 Oct | Rotterdam Alexander 07:36 | +4 min | +4 min |
| Mon 12 Oct | Rotterdam Alexander 07:31 | 0 min | — |
| Fri 9 Oct | Rotterdam Alexander 07:32 | +1 min | +1 min |
| Thu 8 Oct | Rotterdam Alexander 07:31Partial coverage | +1 min | — |
| Wed 7 Oct | Rotterdam Alexander 07:32 | +1 min | — |
| Tue 6 Oct | Rotterdam Alexander 07:31 | 0 min | — |
| Mon 5 Oct | Rotterdam Alexander 12:20 | 0 min | +2 min |
| Fri 2 Oct | Rotterdam Alexander 19:58 | 0 min | +3 min |
| Thu 1 Oct | Rotterdam Alexander 21:23 | +1 min | +3 min |
| Wed 30 Sept | Rotterdam Alexander 19:49 | −2 min | +1 min |
| Tue 29 Sept | Rotterdam Alexander 07:31 | No data | — |
| Mon 28 Sept | Rotterdam Alexander 07:33 | No data | — |
| Fri 25 Sept | Rotterdam Alexander 00:16 | −4 min | +11 min |
| Thu 24 Sept | Rotterdam Alexander 00:59 | −6 min | +5 min |