Train NS 5560 Baarn – Utrecht Centraal

Baarn 17:55 → Utrecht Centraal 18:25 Daily 0 h 30 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:55 from Baarn · Fri 6 Nov

Next departure 17:55 today · Baarn
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 16 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 1 full · 15 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Utrecht Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 11 Oct Max en route +7 min · last fix heading to Utrecht Overvecht +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=2
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 16 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
17:55on time on time
17:59— —
18:02 / 18:03— —
18:05— —
18:10— —
18:14— —
18:18 / 18:21— —
18:25— —

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 NovDen Dolder 18:24No data—
Wed 4 NovBilthoven 18:29Partial coverage0 min—
Tue 3 NovDen Dolder 18:24No data—
Mon 2 NovDen Dolder 18:24No data—
Sun 1 NovUtrecht Overvecht 18:34Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 18:35No data—
Fri 30 OctUtrecht Overvecht 18:35No data—
Thu 29 OctSoestdijk 18:26No data—
Wed 28 OctDen Dolder 18:27No data—
Tue 27 OctSoest Zuid 18:27Partial coverage0 min—
Mon 26 OctSoest Zuid 18:26No data—
Sun 25 OctUtrecht Overvecht 18:35No data—
Sat 24 OctUtrecht Overvecht 18:35Partial coverage0 min—
Fri 23 OctUtrecht Overvecht 18:35No data—
Thu 22 OctUtrecht Overvecht 18:35No data—
Wed 21 OctUtrecht Overvecht 18:34No data—
Tue 20 OctUtrecht Overvecht 18:35Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 18:35Partial coverage0 min—
Sun 18 OctUtrecht Overvecht 18:350 min—
Sat 17 OctUtrecht Overvecht 18:35No data—
Fri 16 OctUtrecht Overvecht 18:30Partial coverage0 min—
Thu 15 OctUtrecht Overvecht 18:35No data—
Wed 14 OctUtrecht Overvecht 18:35No data—
Tue 13 OctUtrecht Overvecht 18:35No data—
Mon 12 OctUtrecht Overvecht 18:32Partial coverage0 min—
Sun 11 OctUtrecht Overvecht 18:41Partial coverage+6 min+7 min
Sat 10 OctUtrecht Overvecht 18:35Partial coverage0 min+1 min
Fri 9 OctUtrecht Overvecht 18:35Partial coverage0 min—
Thu 8 OctSoest 18:27Partial coverage0 min—
Wed 7 OctSoest Zuid 18:26Partial coverage0 min—