Train NS 2812 Utrecht Centraal – Rotterdam Centraal
✓ Today’s run finished
Today, last fix heading to Rotterdam Alexander at 06:47 +1 min
- Utrecht Centraal06:03
- Gouda06:21
- Rotterdam Alexander06:31
- Rotterdam Centraal06:40
Next service: tomorrow 06: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 +9 min · last fix heading to Rotterdam Alexander +9 min
- Wed 4 Nov Max en route +8 min · last fix heading to Rotterdam Alexander +7 min
- Thu 29 Oct Max en route +9 min · last fix heading to Rotterdam Alexander +7 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 15
- 3–10 min 17% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=4
- 75% W n=4
- 75% T n=4
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 18 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:03 | on time | on time | |
| 06:21 / 06:22 | ≈ +1 min | ≈ +3 min | |
| 06:31 | ≈ +1 min | ≈ +5 min | |
| 06:40 | +1 min | +7 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 | Rotterdam Alexander 06:47Partial coverage | +1 min | — |
| Wed 4 Nov | Rotterdam Alexander 06:53 | +7 min | +8 min |
| Tue 3 Nov | Rotterdam Alexander 06:44Partial coverage | 0 min | — |
| Mon 2 Nov | Rotterdam Alexander 07:04Partial coverage | 0 min | — |
| Fri 30 Oct | Rotterdam Alexander 06:46Partial coverage | +1 min | — |
| Thu 29 Oct | Rotterdam Alexander 06:52 | +7 min | +9 min |
| Wed 28 Oct | Rotterdam Alexander 06:46 | 0 min | — |
| Tue 27 Oct | Rotterdam Alexander 06:46Partial coverage | 0 min | — |
| Mon 26 Oct | Rotterdam Alexander 06:51Partial coverage | +9 min | +9 min |
| Fri 16 Oct | Rotterdam Alexander 06:47Partial coverage | +1 min | — |
| Thu 15 Oct | Rotterdam Alexander 06:46Partial coverage | 0 min | — |
| Wed 14 Oct | Rotterdam Alexander 06:46 | +1 min | — |
| Tue 13 Oct | Rotterdam Alexander 06:46 | +1 min | — |
| Mon 12 Oct | Rotterdam Alexander 06:47 | +1 min | +1 min |
| Fri 9 Oct | Rotterdam Alexander 06:46Partial coverage | +1 min | +1 min |
| Thu 8 Oct | Rotterdam Alexander 06:46Partial coverage | 0 min | — |
| Wed 7 Oct | Rotterdam Alexander 06:46 | +2 min | +2 min |
| Tue 6 Oct | Rotterdam Alexander 06:46Partial coverage | +1 min | — |
| Mon 5 Oct | Rotterdam Alexander 06:47 | No data | — |
| Fri 2 Oct | Rotterdam Alexander 06:46 | No data | — |
| Thu 1 Oct | Rotterdam Alexander 06:45 | No data | — |
| Wed 30 Sept | Rotterdam Alexander 06:49 | No data | — |
| Tue 29 Sept | Rotterdam Alexander 06:46 | No data | — |
| Mon 28 Sept | Rotterdam Alexander 06:46 | No data | — |
| Fri 25 Sept | Rotterdam Alexander 06:46 | No data | — |
| Thu 24 Sept | Rotterdam Alexander 06:48 | No data | — |
| Wed 23 Sept | Rotterdam Alexander 06:46 | No data | — |
| Tue 22 Sept | Rotterdam Alexander 06:46 | No data | — |
| Mon 21 Sept | Rotterdam Alexander 06:47 | No data | — |
| Fri 18 Sept | Rotterdam Alexander 06:46 | No data | — |