Train NS 5547 Utrecht Centraal – Baarn

Utrecht Centraal 13:37 → Baarn 14:10 Daily 0 h 33 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:37 from Utrecht Centraal · Thu 5 Nov

Next departure 13:37 today · Utrecht Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 1 full · 15 partial · 13 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 1 full · 17 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Worst days

  • Sat 24 Oct Max en route +5 min · last fix heading to Soestdijk +5 min

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 94% · 17
  • 3–10 min 6% · 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
  • 67% 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, 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
13:37on time on time
13:41— —
13:46— —
13:48 / 13:49— —
13:54— —
13:56 / 14:03— —
14:06— —
14:10— —

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