Train NS 5537 Utrecht Centraal – Baarn

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

✓ Today’s run finished

Today, last fix heading to Soestdijk at 11:44 No data

  1. Utrecht Centraal11:07
  2. Utrecht Overvecht11:11
  3. Bilthoven11:16
  4. Soest Zuid11:24
  5. Soest11:26
  6. Soestdijk11:30
  7. Baarn11:34

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

Next departure 11:07 tomorrow · Utrecht Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 3 full · 14 partial · 13 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 3 full · 15 partial · 69 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: +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=1
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 100% F n=2
  • 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, 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
11:07on time on time
11:11— —
11:16— —
11:18 / 11:19— —
11:24— —
11:26 / 11:27— —
11:30— —
11:34— —

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