Train NS 5564 Baarn – Utrecht Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:55 from Baarn · Thu 5 Nov

Next departure 18:55 today · Baarn
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 14 full · 5 partial · 10 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 16 full · 5 partial · 38 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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:55on time on time
18:59≈ on time ≈ on time
19:02 / 19:03≈ on time ≈ on time
19:05≈ on time ≈ on time
19:10≈ on time ≈ on time
19:14≈ on time ≈ on time
19:18 / 19:21≈ on time ≈ on time
19:25on 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
Wed 4 Nov— 19:290 min—
Tue 3 Nov— 19:24No data—
Mon 2 Nov— 19:290 min—
Sun 1 NovUtrecht Overvecht 19:34Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 19:36Partial coverage+1 min—
Fri 30 Oct— 19:29No data—
Thu 29 Oct— 19:260 min—
Wed 28 Oct— 19:310 min—
Tue 27 Oct— 19:270 min—
Mon 26 Oct— 19:04No data—
Sun 25 OctUtrecht Overvecht 19:35No data—
Sat 24 OctUtrecht Overvecht 19:38No data—
Fri 23 OctUtrecht Overvecht 19:35Partial coverage0 min—
Thu 22 Oct— 19:27No data—
Wed 21 Oct— 19:27No data—
Tue 20 Oct— 19:250 min—
Mon 19 Oct— 19:260 min—
Sun 18 OctUtrecht Overvecht 19:350 min—
Sat 17 OctUtrecht Overvecht 19:35No data—
Fri 16 OctUtrecht Overvecht 19:35Partial coverage0 min—
Thu 15 Oct— 19:29No data—
Wed 14 OctUtrecht Overvecht 19:35No data—
Tue 13 Oct— 19:270 min—
Mon 12 Oct— 19:260 min—
Sun 11 OctUtrecht Overvecht 19:350 min—
Sat 10 OctUtrecht Overvecht 19:36Partial coverage0 min—
Fri 9 Oct— 19:260 min—
Thu 8 Oct— 19:270 min—
Wed 7 Oct— 19:290 min—
Tue 6 Oct— 19:260 min—