Train NS 5581 Utrecht Centraal – Baarn

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 22:07 from Utrecht Centraal · Thu 5 Nov

Full trip card
Next departure 22:07 today · Utrecht Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 12 full · 3 partial · 12 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 14 full · 3 partial · 28 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Wed 7 Oct Max en route +8 min · last fix heading to — +6 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

17 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 67% W n=3
  • 100% T n=1
  • 67% 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, 17 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
Utrecht Centraal
22:07on time on time
Utrecht Overvecht
22:11≈ on time ≈ on time
Bilthoven
22:16≈ on time ≈ +1 min
Den Dolder
22:18 / 22:19≈ on time ≈ +1 min
Soest Zuid
22:24≈ +1 min ≈ +2 min
Soest
22:26 / 22:27≈ +1 min ≈ +2 min
Soestdijk
22:30≈ +1 min ≈ +3 min
Baarn
22:34+1 min +3 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

DateLast stopFinalMax
Wed 4 Nov— 22:34+1 min—
Mon 2 Nov— 22:38+1 min+1 min
Sun 1 NovSoestdijk 22:44Partial coverage+1 min+1 min
Sat 31 OctSoestdijk 22:44Partial coverage0 min—
Fri 30 Oct— 22:36No data—
Wed 28 Oct— 22:350 min—
Tue 27 Oct— 22:36No data—
Mon 26 Oct— 22:36No data—
Sun 25 OctSoestdijk 22:48No data—
Sat 24 OctSoestdijk 22:45Partial coverage0 min—
Fri 23 Oct— 22:40+3 min+3 min
Thu 22 Oct— 22:53No data—
Wed 21 Oct— 22:38No data—
Tue 20 Oct— 22:35No data—
Mon 19 Oct— 22:35No data—
Sun 18 OctSoestdijk 22:45+1 min+1 min
Sat 17 OctSoestdijk 22:44No data—
Fri 16 Oct— 22:37+1 min+1 min
Thu 15 Oct— 22:37No data—
Wed 14 Oct— 22:42No data—
Tue 13 Oct— 22:36No data—
Mon 12 Oct— 22:38+2 min+2 min
Sun 11 OctSoestdijk 22:45+1 min+1 min
Sat 10 Oct— 22:360 min—
Fri 9 Oct— 22:36+1 min+1 min
Thu 8 Oct— 22:360 min—
Wed 7 Oct— 22:46+6 min+8 min
Tue 6 Oct— 22:350 min—
Mon 5 Oct— 22:40+2 min+2 min
Sun 4 OctSoestdijk 22:44No data—