Train NS 5570 Baarn – Utrecht Centraal

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 20:25 from Baarn · Tue 17 Nov

Next departure 20:25 today · Baarn
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 11 full · 7 partial · 7 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 19 full · 9 partial · 21 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 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

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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 100% W n=4
  • 100% T n=2
  • 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, 28 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
20:25on time on time
20:29≈ on time ≈ on time
20:32 / 20:33≈ on time ≈ on time
20:35≈ on time ≈ on time
20:40≈ on time ≈ +1 min
20:44≈ on time ≈ +1 min
20:48 / 20:51≈ on time ≈ +1 min
20:55on time +1 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
Sun 15 NovUtrecht Overvecht 21:04Partial coverage0 min—
Sat 14 NovUtrecht Overvecht 21:04Partial coverage+1 min+2 min
Fri 13 Nov— 20:54+2 min+2 min
Thu 12 Nov— 20:540 min—
Wed 11 Nov— 20:570 min—
Tue 10 Nov— 21:04+4 min+4 min
Mon 9 Nov— 20:540 min—
Sun 8 NovUtrecht Overvecht 21:04Partial coverage0 min—
Sat 7 NovUtrecht Overvecht 21:04Partial coverage0 min—
Fri 6 Nov— 20:540 min—
Thu 5 Nov— 20:55No data—
Wed 4 Nov— 20:58+1 min+1 min
Tue 3 Nov— 20:54No data—
Sun 1 NovUtrecht Overvecht 21:04Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 21:05Partial coverage0 min—
Fri 30 Oct— 20:56No data—
Wed 28 Oct— 20:560 min—
Tue 27 Oct— 20:570 min—
Mon 26 Oct— 20:57No data—
Sun 25 OctUtrecht Overvecht 21:05No data—
Sat 24 OctUtrecht Overvecht 21:05Partial coverage0 min—
Fri 23 Oct— 20:570 min—
Thu 22 Oct— 20:57No data—
Wed 21 Oct— 20:59No data—
Mon 19 Oct— 21:010 min—
Sun 18 OctUtrecht Overvecht 21:050 min—
Sat 17 OctUtrecht Overvecht 21:05No data—
Fri 16 Oct— 20:560 min—
Thu 15 Oct— 20:58No data—
Wed 14 Oct— 20:56No data—