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