Train NS 5545 Utrecht Centraal – Baarn

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

✓ Today’s run finished

Today, last fix heading to Soestdijk at 13:49 No data

  1. Utrecht Centraal13:07
  2. Utrecht Overvecht13:11
  3. Bilthoven13:16
  4. Soest Zuid13:24
  5. Soest13:26
  6. Soestdijk13:36
  7. Baarn13:40

Next service: tomorrow 13:07 from Utrecht Centraal · Fri 6 Nov

Next departure 13:07 tomorrow · Utrecht Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 16 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 71 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=1
  • 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, 16 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
13:07on time on time
13:11≈ on time ≈ on time
13:16≈ on time ≈ on time
13:18 / 13:19≈ on time ≈ on time
13:24≈ on time ≈ on time
13:26 / 13:33≈ on time ≈ on time
13:36≈ on time ≈ on time
13:40on time on time

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