Train NS 5523 Utrecht Centraal – Baarn

Utrecht Centraal 07:37 → Baarn 08:04 Mon, Tue, Wed, Thu, Fri, Sat 0 h 27 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Soestdijk at 08:14 No data

  1. Utrecht Centraal07:37
  2. Utrecht Overvecht07:41
  3. Bilthoven07:46
  4. Soest Zuid07:54
  5. Soest07:56
  6. Soestdijk08:00
  7. Baarn08:04

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

Next departure 07:37 tomorrow · Utrecht Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 1 full · 17 partial · 8 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 1 full · 18 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 +8 min · last fix heading to Soestdijk +8 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=4
  • 100% T n=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=4
  • 75% S n=4
  • — S n=0

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
07:37on time on time
07:41— —
07:46— —
07:48 / 07:49— —
07:54— —
07:56 / 07:57— —
08:00— —
08:04— —

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