Train NS 2860 Utrecht Centraal – Rotterdam Centraal
It has not run yet today
Last recorded run: Thursday 5 November 0 min
Next service: today 18:03 from Utrecht Centraal · Fri 6 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
- Mon 26 Oct Max en route +12 min · last fix heading to Utrecht Centraal +12 min
- Tue 6 Oct Max en route +7 min · last fix heading to Utrecht Centraal +7 min
- Wed 28 Oct Max en route +6 min · last fix heading to Utrecht Centraal +6 min
- Sun 1 Nov Max en route +5 min · last fix heading to Rotterdam Alexander +5 min
- Thu 8 Oct Max en route +4 min · last fix heading to Utrecht Centraal +4 min
Distribution · 90 days
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 63% · 10
- 3–10 min 31% · 5
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 50% M n=4
- 0% T n=1
- 67% W n=3
- 67% T n=3
- 100% F n=2
- 100% S n=1
- 50% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 16 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 |
|---|---|---|---|
| 18:03 | on time | +1 min | |
| 18:21 / 18:22 | ≈ on time | ≈ +1 min | |
| 18:31 | ≈ on time | ≈ +2 min | |
| 18:40 | on time | +3 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 |
|---|---|---|---|
| Thu 5 Nov | Utrecht Centraal 18:39Partial coverage | 0 min | — |
| Wed 4 Nov | Utrecht Centraal 18:42 | No data | — |
| Tue 3 Nov | Utrecht Centraal 18:44 | No data | — |
| Mon 2 Nov | Utrecht Centraal 18:43Partial coverage | +1 min | +1 min |
| Sun 1 Nov | Rotterdam Alexander 18:49 | +5 min | +5 min |
| Sat 31 Oct | Rotterdam Alexander 18:46 | No data | — |
| Fri 30 Oct | Rotterdam Alexander 18:45 | No data | — |
| Thu 29 Oct | — 18:48 | +2 min | +2 min |
| Wed 28 Oct | Utrecht Centraal 18:47Partial coverage | +6 min | +6 min |
| Tue 27 Oct | Utrecht Centraal 18:42 | No data | — |
| Mon 26 Oct | Utrecht Centraal 19:03Partial coverage | +12 min | +12 min |
| Fri 16 Oct | Rotterdam Alexander 18:46 | 0 min | — |
| Thu 15 Oct | Gouda 18:42 | No data | — |
| Wed 14 Oct | Utrecht Centraal 19:04 | 0 min | — |
| Tue 13 Oct | Rotterdam Alexander 18:45 | No data | — |
| Mon 12 Oct | Rotterdam Alexander 18:56 | 0 min | — |
| Sun 11 Oct | Rotterdam Alexander 18:45 | 0 min | — |
| Sat 10 Oct | Rotterdam Alexander 18:46 | 0 min | — |
| Fri 9 Oct | Rotterdam Alexander 18:45 | 0 min | — |
| Thu 8 Oct | Utrecht Centraal 18:49Partial coverage | +4 min | +4 min |
| Wed 7 Oct | Utrecht Centraal 18:46Partial coverage | +3 min | +3 min |
| Tue 6 Oct | Utrecht Centraal 18:47Partial coverage | +7 min | +7 min |
| Mon 5 Oct | Utrecht Centraal 18:49Partial coverage | +4 min | +4 min |
| Sun 4 Oct | Rotterdam Alexander 18:48 | No data | — |
| Sat 3 Oct | Rotterdam Alexander 18:46 | No data | — |
| Fri 2 Oct | Rotterdam Alexander 18:45 | No data | — |
| Thu 1 Oct | Utrecht Centraal 18:18 | No data | — |
| Wed 30 Sept | Utrecht Centraal 18:17 | No data | — |
| Tue 29 Sept | Utrecht Centraal 18:17 | No data | — |
| Mon 28 Sept | Utrecht Centraal 18:17 | No data | — |