Train NS 5589 Utrecht Centraal – Baarn

Utrecht Centraal 00:07 → Baarn 00:36 Daily 0 h 29 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:42 +2 min

  1. Utrecht Centraal00:07
  2. Utrecht Overvecht00:11
  3. Bilthoven00:16
  4. Soest Zuid00:24
  5. Soest00:26
  6. Soestdijk00:30
  7. Baarn00:36

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

Next departure 00:07 tomorrow · Utrecht Centraal
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 21 full · 3 partial · 1 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 21 full · 4 partial · 10 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

  • Tue 3 Nov Max en route +6 min · last fix heading to — +6 min
  • Sat 24 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
00:07on time on time
00:11≈ on time ≈ on time
00:16≈ on time ≈ +1 min
00:18 / 00:19≈ on time ≈ +1 min
00:24≈ on time ≈ +1 min
00:26 / 00:27≈ on time ≈ +1 min
00:30≈ on time ≈ +2 min
00:36on time +2 min

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 Nov— 00:42+2 min+2 min
Wed 4 Nov— 00:380 min—
Tue 3 Nov— 00:48+6 min+6 min
Sun 1 NovSoestdijk 00:44Partial coverage0 min—
Sat 31 Oct— 00:380 min—
Fri 30 Oct— 00:370 min—
Thu 29 Oct— 00:370 min—
Wed 28 Oct— 00:440 min—
Tue 27 Oct— 00:370 min—
Sun 25 OctSoestdijk 00:450 min—
Sat 24 Oct— 00:38+4 min+4 min
Fri 23 Oct— 00:380 min—
Thu 22 Oct— 00:38No data—
Wed 21 Oct— 00:440 min—
Tue 20 Oct— 00:360 min—
Sun 18 OctSoestdijk 00:44Partial coverage0 min—
Sat 17 OctSoest 00:410 min—
Fri 16 Oct— 00:370 min—
Thu 15 Oct— 00:380 min—
Wed 14 Oct— 00:480 min—
Tue 13 Oct— 00:370 min—
Sun 11 OctSoestdijk 00:45Partial coverage0 min—
Sat 10 Oct— 00:36+1 min+1 min
Thu 8 Oct— 00:370 min—
Wed 7 Oct— 00:370 min—
Tue 6 OctUtrecht Overvecht 00:37Partial coverage0 min—
Sun 4 OctSoestdijk 00:44No data—
Sat 3 OctSoestdijk 00:44No data—
Sun 20 SeptSoestdijk 00:44No data—
Sun 13 SeptSoestdijk 00:44No data—