Train NS 5519 Utrecht Centraal – Baarn

Utrecht Centraal 06:37 → Baarn 07:04 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 06:37 from Utrecht Centraal · Thu 5 Nov

Next departure 06:37 today · Utrecht Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 2 full · 18 partial · 1 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 2 full · 19 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Baarn, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +3 min · last fix heading to Soestdijk +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Soestdijk +3 min

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 90% · 19
  • 3–10 min 10% · 2
  • 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
  • 75% T n=4
  • 75% 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
06:37on time on time
06:41— —
06:46— —
06:48 / 06:49— —
06:54— —
06:56 / 06:57— —
07:00— —
07:04— —

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 NovSoestdijk 07:14Partial coverage0 min—
Tue 3 NovSoestdijk 07:14Partial coverage+1 min—
Mon 2 NovSoestdijk 07:18No data—
Fri 30 OctSoestdijk 07:15Partial coverage+1 min+1 min
Thu 29 OctSoestdijk 07:16Partial coverage+1 min+1 min
Wed 28 OctSoestdijk 07:16Partial coverage+1 min+1 min
Tue 27 OctSoestdijk 07:200 min+5 min
Mon 26 OctSoestdijk 07:14Partial coverage0 min—
Fri 23 OctSoestdijk 07:17Partial coverage+3 min+3 min
Thu 22 OctSoestdijk 07:15Partial coverage+1 min—
Wed 21 OctSoestdijk 07:14Partial coverage0 min—
Tue 20 OctSoestdijk 07:14Partial coverage0 min—
Mon 19 OctSoestdijk 07:140 min—
Fri 16 OctSoestdijk 07:15Partial coverage+1 min+1 min
Thu 15 OctSoestdijk 07:16Partial coverage+2 min+2 min
Wed 14 OctSoestdijk 07:15Partial coverage+1 min—
Tue 13 OctSoestdijk 07:16Partial coverage+2 min+2 min
Mon 12 OctSoestdijk 07:15Partial coverage+1 min—
Fri 9 OctSoestdijk 07:17Partial coverage+2 min+2 min
Thu 8 OctSoestdijk 07:17Partial coverage+3 min+3 min
Wed 7 OctSoestdijk 07:17Partial coverage+3 min+3 min
Tue 6 OctSoestdijk 07:15Partial coverage+1 min—
Mon 5 OctSoestdijk 07:15No data—
Fri 2 OctSoestdijk 07:14No data—
Thu 1 OctSoestdijk 07:14No data—
Wed 30 SeptSoestdijk 07:15No data—
Tue 29 SeptSoestdijk 07:14No data—
Mon 28 SeptSoestdijk 07:14No data—
Fri 25 SeptSoestdijk 07:15No data—
Thu 24 SeptSoestdijk 07:15No data—