Train NS 2050 Utrecht Centraal – Rotterdam Centraal
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 15:48 from Utrecht Centraal · Thu 5 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
- Tue 29 Sept Max en route +33 min · last fix heading to Rotterdam Alexander +33 min
- Sun 30 Aug Max en route +26 min · last fix heading to Rotterdam Alexander +23 min
- Tue 25 Aug Max en route +7 min · last fix heading to Rotterdam Alexander +6 min
- Sat 26 Sept Max en route +5 min · last fix heading to Rotterdam Alexander +5 min
Distribution · 90 days
60 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 30% · 18
- On time 63% · 38
- 3–10 min 3% · 2
- 10–30 min 2% · 1
- 30+ min 2% · 1
On-time by weekday
- 100% M n=11
- 80% T n=10
- 100% W n=7
- 100% T n=8
- 100% F n=8
- 89% S n=9
- 86% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 60 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 |
|---|---|---|---|
| 15:48 | on time | on time | |
| 16:06 / 16:07 | ≈ on time | ≈ +1 min | |
| 16:16 | ≈ on time | ≈ +1 min | |
| 16: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 4 Nov | Rotterdam Alexander 16:29Partial coverage | 0 min | — |
| Tue 3 Nov | Rotterdam Alexander 16:29 | No data | — |
| Mon 2 Nov | Rotterdam Alexander 16:32 | No data | — |
| Sun 1 Nov | Rotterdam Alexander 16:32 | +1 min | — |
| Sat 31 Oct | Rotterdam Alexander 16:30 | 0 min | — |
| Fri 30 Oct | Rotterdam Alexander 16:30 | No data | — |
| Thu 29 Oct | Rotterdam Alexander 16:31 | No data | — |
| Wed 28 Oct | Rotterdam Alexander 16:31Partial coverage | 0 min | — |
| Tue 27 Oct | Rotterdam Alexander 16:37 | 0 min | — |
| Mon 26 Oct | Rotterdam Alexander 16:34 | 0 min | — |
| Sat 17 Oct | Delft 17:04 | 0 min | — |
| Fri 16 Oct | Rotterdam Alexander 16:30 | No data | — |
| Thu 15 Oct | Rotterdam Alexander 16:34 | No data | — |
| Wed 14 Oct | Rotterdam Alexander 16:30 | No data | — |
| Tue 13 Oct | Rotterdam Alexander 16:31Partial coverage | 0 min | — |
| Mon 12 Oct | Rotterdam Alexander 16:31 | +1 min | — |
| Sun 11 Oct | Rotterdam Alexander 16:31 | +1 min | — |
| Sat 10 Oct | Rotterdam Alexander 16:31 | 0 min | — |
| Fri 9 Oct | Rotterdam Alexander 16:31 | +1 min | — |
| Thu 8 Oct | Rotterdam Alexander 16:32Partial coverage | 0 min | — |
| Wed 7 Oct | Rotterdam Alexander 16:31Partial coverage | +2 min | +2 min |
| Tue 6 Oct | Rotterdam Alexander 16:31Partial coverage | 0 min | — |
| Mon 5 Oct | Rotterdam Alexander 16:28 | 0 min | — |
| Sun 4 Oct | Rotterdam Alexander 16:30 | No data | — |
| Sat 3 Oct | Rotterdam Alexander 16:31 | −1 min | — |
| Fri 2 Oct | Rotterdam Alexander 00:26 | −2 min | +2 min |
| Thu 1 Oct | Rotterdam Alexander 00:15 | −7 min | +2 min |
| Wed 30 Sept | Rotterdam Alexander 16:30 | No data | — |
| Tue 29 Sept | Rotterdam Alexander 16:34 | +33 min | +33 min |
| Mon 28 Sept | Rotterdam Alexander 00:41 | 0 min | +6 min |