Train NS 5567 Utrecht Centraal – Baarn

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 18:37 from Utrecht Centraal · Sat 14 Nov

Next departure 18:37 today · Utrecht Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 11 full · 8 partial · 8 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 16 full · 10 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Tue 10 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 75% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=5
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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
18:37on time on time
18:41≈ on time ≈ on time
18:46≈ on time ≈ on time
18:48 / 18:49≈ on time ≈ on time
18:54≈ on time ≈ on time
18:56 / 19:03≈ on time ≈ on time
19:06≈ on time ≈ on time
19:10on time on time

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
Fri 13 NovSoest Zuid 19:12Partial coverage0 min—
Thu 12 Nov— 19:130 min—
Wed 11 Nov— 19:090 min—
Tue 10 Nov— 19:23+6 min+6 min
Mon 9 Nov— 19:120 min—
Sun 8 NovSoestdijk 19:19Partial coverage0 min—
Sat 7 NovSoestdijk 19:19Partial coverage0 min—
Fri 6 NovBilthoven 19:09Partial coverage+1 min—
Thu 5 Nov— 19:09No data—
Wed 4 Nov— 19:120 min—
Sun 1 NovSoestdijk 19:19Partial coverage0 min—
Sat 31 OctSoestdijk 19:20No data—
Fri 30 OctSoest Zuid 19:16No data—
Thu 29 Oct— 19:110 min—
Wed 28 Oct— 19:110 min—
Tue 27 Oct— 19:120 min—
Mon 26 Oct— 19:110 min—
Sun 25 OctSoestdijk 19:20No data—
Sat 24 OctSoestdijk 19:20No data—
Fri 23 OctSoestdijk 19:15Partial coverage+1 min—
Thu 22 OctUtrecht Overvecht 19:12No data—
Wed 21 OctUtrecht Centraal 19:12No data—
Tue 20 OctBilthoven 19:11Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 18:550 min—
Sun 18 OctSoestdijk 19:150 min—
Sat 17 OctSoestdijk 19:17No data—
Fri 16 OctSoestdijk 19:20Partial coverage0 min—
Thu 15 Oct— 19:11No data—
Wed 14 OctSoestdijk 19:20No data—
Tue 13 OctUtrecht Centraal 19:11No data—