Train NS 5529 Utrecht Centraal – Baarn

Utrecht Centraal 09:07 → Baarn 09:34 Daily 0 h 27 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 09:07 from Utrecht Centraal · Sat 7 Nov

Next departure 09:07 today · Utrecht Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 3 full · 13 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 3 full · 16 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Sat 10 Oct 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=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 75% S n=4
  • 100% 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.

StopSched.Usually 9 days in 10
09:07on time on time
09:11— —
09:16— —
09:18 / 09:19— —
09:24— —
09:26 / 09:27— —
09:30— —
09:34— —

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

DateLast stopFinalMax
Fri 6 NovSoestdijk 09:49No data—
Thu 5 NovSoestdijk 09:44No data—
Wed 4 NovSoestdijk 09:44Partial coverage0 min—
Tue 3 NovSoestdijk 09:49No data—
Mon 2 NovSoestdijk 09:44Partial coverage0 min—
Sun 1 NovSoestdijk 09:440 min—
Sat 31 OctSoestdijk 09:45Partial coverage+1 min+1 min
Fri 30 OctSoestdijk 09:44No data—
Thu 29 OctSoestdijk 09:45Partial coverage0 min—
Wed 28 OctSoestdijk 09:44Partial coverage0 min—
Tue 27 OctSoestdijk 09:44Partial coverage0 min—
Mon 26 OctSoestdijk 09:45No data—
Sun 25 OctSoestdijk 09:44No data—
Sat 24 OctSoestdijk 09:47Partial coverage+3 min+3 min
Fri 23 OctSoestdijk 09:45No data—
Thu 22 OctSoestdijk 09:44No data—
Wed 21 OctSoestdijk 09:48No data—
Tue 20 OctSoestdijk 09:45Partial coverage0 min—
Mon 19 OctSoestdijk 09:45Partial coverage0 min—
Sun 18 OctSoestdijk 09:440 min—
Sat 17 OctSoestdijk 09:45+1 min+1 min
Fri 16 OctSoestdijk 09:44Partial coverage0 min—
Thu 15 OctSoest 10:58No data—
Wed 14 OctSoestdijk 09:44No data—
Tue 13 OctSoestdijk 09:44No data—
Mon 12 OctSoestdijk 09:45No data—
Sun 11 OctSoestdijk 09:45Partial coverage0 min—
Sat 10 OctSoestdijk 09:48Partial coverage+4 min+4 min
Fri 9 OctSoestdijk 09:47Partial coverage+3 min+3 min
Thu 8 OctSoestdijk 09:44Partial coverage0 min—