Train NS 5539 Utrecht Centraal – Baarn
✓ Today’s run finished
Today, last fix heading to Soestdijk at 12:14 No data
- Utrecht Centraal11:37
- Utrecht Overvecht11:41
- Bilthoven11:46
- Soest Zuid11:54
- Soest11:56
- Soestdijk12:00
- Baarn12:04
Next service: tomorrow 11:37 from Utrecht Centraal · Fri 6 Nov
Last 30 days
Arrival delay at Baarn, 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 +4 min · last fix heading to Soestdijk +4 min
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 18
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=4
- 100% W n=3
- 100% T n=2
- 100% F n=1
- 100% S n=3
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 11:37 | on time | on time | |
| 11:41 | ≈ on time | ≈ +2 min | |
| 11:46 | ≈ on time | ≈ +2 min | |
| 11:48 / 11:49 | ≈ on time | ≈ +2 min | |
| 11:54 | ≈ on time | ≈ +2 min | |
| 11:56 / 11:57 | ≈ on time | ≈ +2 min | |
| 12:00 | ≈ on time | ≈ +2 min | |
| 12:04 | 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 |
|---|---|---|---|
| Thu 5 Nov | Soestdijk 12:14 | No data | — |
| Wed 4 Nov | Soestdijk 12:14Partial coverage | +1 min | +1 min |
| Tue 3 Nov | Soestdijk 12:14 | 0 min | — |
| Mon 2 Nov | Soestdijk 12:14Partial coverage | 0 min | — |
| Sun 1 Nov | Soestdijk 12:19 | +4 min | +4 min |
| Sat 31 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Fri 30 Oct | Soestdijk 12:14 | No data | — |
| Thu 29 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Wed 28 Oct | Soestdijk 12:14 | No data | — |
| Tue 27 Oct | Soestdijk 12:15 | 0 min | — |
| Mon 26 Oct | Soestdijk 12:15 | No data | — |
| Sun 25 Oct | Soestdijk 12:14 | No data | — |
| Sat 24 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Fri 23 Oct | Soestdijk 12:15 | No data | — |
| Thu 22 Oct | Soestdijk 12:15 | No data | — |
| Wed 21 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Tue 20 Oct | Soestdijk 12:14 | 0 min | — |
| Mon 19 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Sun 18 Oct | Soestdijk 12:15 | 0 min | — |
| Sat 17 Oct | Soestdijk 12:17 | No data | — |
| Fri 16 Oct | Soestdijk 12:14 | No data | — |
| Thu 15 Oct | Soestdijk 12:14 | No data | — |
| Wed 14 Oct | Soestdijk 12:15 | No data | — |
| Tue 13 Oct | Soestdijk 12:15 | No data | — |
| Mon 12 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Sun 11 Oct | Soestdijk 12:16Partial coverage | +2 min | +2 min |
| Sat 10 Oct | Soestdijk 12:15Partial coverage | 0 min | — |
| Fri 9 Oct | Soestdijk 12:14Partial coverage | 0 min | — |
| Thu 8 Oct | Soestdijk 12:16Partial coverage | +2 min | +2 min |
| Wed 7 Oct | Soestdijk 12:14Partial coverage | 0 min | — |