Train NS 5517 Utrecht Centraal – Baarn

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

✓ Today’s run finished

Today, last fix heading to Soestdijk at 06:44 0 min

  1. Utrecht Centraal06:07
  2. Utrecht Overvecht06:11
  3. Bilthoven06:16
  4. Soest Zuid06:24
  5. Soest06:26
  6. Soestdijk06:30
  7. Baarn06:34

Next service: tomorrow 06:07 from Utrecht Centraal · Thu 29 Oct

Next departure 06:07 tomorrow · Utrecht Centraal
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 5 full · 12 partial · 5 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 5 full · 12 partial · 46 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

  • Wed 14 Oct Max en route +7 min · last fix heading to Soestdijk +7 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Soestdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 75% W n=4
  • 67% T n=3
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

StopSched.
06:07
06:11
06:16
06:18 / 06:19
06:24
06:26 / 06:27
06:30
06: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.

Recent runs

DateLast stopFinalMax
Wed 28 OctSoestdijk 06:44Partial coverage0 min—
Tue 27 OctSoestdijk 06:44Partial coverage0 min—
Mon 26 OctSoestdijk 06:440 min—
Fri 23 OctSoestdijk 06:45Partial coverage0 min—
Thu 22 OctSoestdijk 06:47Partial coverage+3 min+3 min
Wed 21 OctSoestdijk 06:44Partial coverage0 min—
Tue 20 OctSoestdijk 06:44Partial coverage0 min—
Mon 19 OctSoestdijk 06:450 min—
Fri 16 OctSoestdijk 06:440 min—
Thu 15 OctSoestdijk 06:44Partial coverage0 min—
Wed 14 OctSoestdijk 06:51Partial coverage+7 min+7 min
Tue 13 OctSoestdijk 06:45Partial coverage+1 min+1 min
Mon 12 OctSoestdijk 06:450 min—
Fri 9 OctSoestdijk 06:44Partial coverage0 min—
Thu 8 OctSoestdijk 06:45+1 min+1 min
Wed 7 OctSoestdijk 06:44Partial coverage0 min—
Tue 6 OctSoestdijk 06:45Partial coverage+1 min+1 min
Mon 5 OctSoestdijk 06:45No data—
Fri 2 OctSoestdijk 06:47No data—
Thu 1 OctSoestdijk 06:45No data—
Wed 30 SeptSoestdijk 06:46No data—
Tue 29 SeptSoestdijk 06:45No data—
Mon 28 SeptSoestdijk 06:45No data—
Fri 25 SeptSoestdijk 06:44No data—
Thu 24 SeptSoestdijk 06:46No data—
Wed 23 SeptSoestdijk 06:44No data—
Tue 22 SeptSoestdijk 06:44No data—
Mon 21 SeptSoestdijk 06:45No data—
Fri 18 SeptSoestdijk 06:44No data—
Thu 17 SeptSoestdijk 06:45No data—