Train NS 5566 Baarn – Utrecht Centraal
✓ Today’s run finished
Today, last fix heading to — at 19:54 0 min
- Baarn19:25
- Soestdijk19:29
- Soest19:32
- Den Dolder19:40
- Bilthoven19:44
- Utrecht Overvecht19:48
- Utrecht Centraal19:55
Next service: tomorrow 19:25 from Baarn · Wed 18 Nov
Last 30 days
Arrival delay at Utrecht 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 15 Nov Max en route +4 min · last fix heading to Utrecht Overvecht +4 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 97% · 31
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=5
- 100% W n=5
- 100% T n=4
- 100% F n=5
- 100% S n=4
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 32 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 |
|---|---|---|---|
| 19:25 | on time | on time | |
| 19:29 | ≈ on time | ≈ on time | |
| 19:32 / 19:33 | ≈ on time | ≈ on time | |
| 19:35 | ≈ on time | ≈ on time | |
| 19:40 | ≈ on time | ≈ on time | |
| 19:44 | ≈ on time | ≈ on time | |
| 19:48 / 19:51 | ≈ on time | ≈ on time | |
| 19:55 | on time | on time |
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 |
|---|---|---|---|
| Tue 17 Nov | — 19:54 | 0 min | — |
| Mon 16 Nov | — 19:57 | 0 min | — |
| Sun 15 Nov | Utrecht Overvecht 20:09Partial coverage | +4 min | +4 min |
| Sat 14 Nov | Utrecht Overvecht 20:04Partial coverage | 0 min | — |
| Fri 13 Nov | — 19:54 | 0 min | — |
| Thu 12 Nov | — 19:58 | 0 min | — |
| Wed 11 Nov | — 19:54 | 0 min | +2 min |
| Tue 10 Nov | — 19:54 | 0 min | — |
| Mon 9 Nov | — 19:57 | +2 min | +2 min |
| Sun 8 Nov | Utrecht Overvecht 20:04Partial coverage | 0 min | — |
| Sat 7 Nov | Utrecht Overvecht 20:04Partial coverage | 0 min | — |
| Fri 6 Nov | — 19:54 | 0 min | — |
| Thu 5 Nov | — 19:54 | 0 min | — |
| Wed 4 Nov | — 19:57 | 0 min | — |
| Tue 3 Nov | — 19:54 | 0 min | — |
| Mon 2 Nov | — 19:54 | No data | — |
| Sun 1 Nov | Utrecht Overvecht 20:04Partial coverage | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 20:05Partial coverage | 0 min | — |
| Fri 30 Oct | — 19:56 | No data | — |
| Thu 29 Oct | — 19:56 | 0 min | — |
| Wed 28 Oct | — 19:56 | 0 min | — |
| Tue 27 Oct | — 19:57 | 0 min | — |
| Mon 26 Oct | Utrecht Overvecht 19:56Partial coverage | 0 min | — |
| Sun 25 Oct | Utrecht Overvecht 20:05 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 20:05 | No data | — |
| Fri 23 Oct | Baarn 19:56Partial coverage | 0 min | — |
| Thu 22 Oct | — 19:59 | No data | — |
| Wed 21 Oct | — 19:59 | No data | — |
| Tue 20 Oct | — 19:57 | No data | — |
| Mon 19 Oct | — 19:57 | No data | — |