Train NS 5512 Baarn – Utrecht Centraal

Baarn 05:54 → Utrecht Centraal 06:25 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 05:54 from Baarn · Thu 5 Nov

Next departure 05:54 today · Baarn
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 1 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 9 full · 12 partial · 41 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: 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=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

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
05:54on time on time
05:59≈ on time ≈ on time
06:02 / 06:03≈ on time ≈ on time
06:05≈ on time ≈ on time
06:10≈ on time ≈ on time
06:14≈ on time ≈ on time
06:18 / 06:21≈ on time ≈ on time
06: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 NovUtrecht Overvecht 06:34Partial coverage0 min—
Tue 3 NovUtrecht Overvecht 06:34Partial coverage+2 min+2 min
Mon 2 NovUtrecht Overvecht 06:34No data—
Fri 30 OctUtrecht Overvecht 06:350 min—
Thu 29 OctUtrecht Overvecht 06:350 min—
Wed 28 OctUtrecht Overvecht 06:35Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 06:35Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 06:36Partial coverage+1 min+2 min
Fri 23 OctUtrecht Overvecht 06:350 min—
Thu 22 OctUtrecht Overvecht 06:350 min—
Wed 21 OctUtrecht Overvecht 06:35Partial coverage0 min—
Tue 20 OctUtrecht Overvecht 06:35Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 06:350 min—
Fri 16 OctUtrecht Overvecht 06:350 min—
Thu 15 OctUtrecht Overvecht 06:350 min—
Wed 14 OctUtrecht Overvecht 06:35Partial coverage0 min—
Tue 13 OctUtrecht Overvecht 06:35Partial coverage0 min—
Mon 12 OctUtrecht Overvecht 06:35Partial coverage0 min—
Fri 9 OctUtrecht Overvecht 06:350 min—
Thu 8 OctUtrecht Overvecht 06:350 min—
Wed 7 OctUtrecht Overvecht 06:35Partial coverage0 min—
Tue 6 OctUtrecht Overvecht 06:36Partial coverage+1 min+2 min
Mon 5 OctUtrecht Overvecht 06:36No data—
Fri 2 OctUtrecht Overvecht 06:35No data—
Thu 1 OctUtrecht Overvecht 06:35No data—
Wed 30 SeptUtrecht Overvecht 06:35No data—
Tue 29 SeptUtrecht Overvecht 06:35No data—
Mon 28 SeptUtrecht Overvecht 06:35No data—
Fri 25 SeptUtrecht Overvecht 06:35No data—
Thu 24 SeptUtrecht Overvecht 06:39No data—