Train NS 5568 Baarn – Utrecht Centraal

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 19:55 from Baarn · Tue 17 Nov

Next departure 19:55 today · Baarn
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 14 full · 6 partial · 9 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 23 full · 8 partial · 25 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

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

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

On-time by weekday

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

Stops and timetable

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

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