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