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