Train NS 5561 Utrecht Centraal – Baarn

Utrecht Centraal 17:07 → Baarn 17:40 Daily 0 h 33 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Soestdijk at 17:49 +1 min

  1. Utrecht Centraal17:07
  2. Utrecht Overvecht17:11
  3. Bilthoven17:16
  4. Soest Zuid17:24
  5. Soest17:26
  6. Soestdijk17:36
  7. Baarn17:40

Next service: tomorrow 17:07 from Utrecht Centraal · Sun 8 Nov

Next departure 17:07 tomorrow · Utrecht Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 16 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 1 full · 17 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=3
  • 100% S n=3
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 18 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
17:07on time on time
17:11— —
17:16— —
17:18 / 17:19— —
17:24— —
17:26 / 17:33— —
17:36— —
17:40— —

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
Sat 7 NovSoestdijk 17:49Partial coverage+1 min+1 min
Fri 6 NovSoestdijk 17:49Partial coverage+1 min—
Thu 5 NovSoestdijk 17:49No data—
Wed 4 NovSoestdijk 17:49Partial coverage0 min—
Tue 3 NovSoestdijk 17:49No data—
Mon 2 NovSoestdijk 17:49No data—
Sun 1 NovSoestdijk 17:51Partial coverage+1 min+1 min
Sat 31 OctSoestdijk 17:50No data—
Fri 30 OctSoestdijk 17:50No data—
Thu 29 OctSoestdijk 17:50No data—
Wed 28 OctSoestdijk 17:50No data—
Tue 27 OctSoestdijk 17:50Partial coverage0 min—
Mon 26 OctSoestdijk 17:50No data—
Sun 25 OctSoestdijk 17:51No data—
Sat 24 OctSoestdijk 17:50Partial coverage0 min—
Fri 23 OctSoestdijk 17:50No data—
Thu 22 OctSoestdijk 17:44No data—
Wed 21 OctSoestdijk 17:50No data—
Tue 20 OctSoestdijk 17:50Partial coverage0 min—
Mon 19 OctSoestdijk 17:50Partial coverage0 min—
Sun 18 OctSoestdijk 17:44No data—
Sat 17 OctSoestdijk 17:45No data—
Fri 16 OctSoestdijk 17:51Partial coverage0 min—
Thu 15 OctSoestdijk 17:50No data—
Wed 14 OctSoestdijk 17:51Partial coverage0 min—
Tue 13 OctSoestdijk 17:50No data—
Mon 12 OctSoestdijk 17:50Partial coverage0 min—
Sun 11 OctSoestdijk 17:51Partial coverage0 min—
Sat 10 OctSoestdijk 17:51Partial coverage+1 min+1 min
Fri 9 OctSoestdijk 17:50Partial coverage0 min—