Train NS 5524 Baarn – Utrecht Centraal

Baarn 08:49 → Utrecht Centraal 09:25 Daily 0 h 36 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Utrecht Overvecht at 09:34 0 min

  1. Baarn08:49
  2. Soestdijk08:53
  3. Soest08:56
  4. Den Dolder09:10
  5. Bilthoven09:13
  6. Utrecht Overvecht09:18
  7. Utrecht Centraal09:25

Next service: tomorrow 08:49 from Baarn · Wed 18 Nov

Next departure 08:49 tomorrow · Baarn
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 1 full · 19 partial · 10 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 3 full · 27 partial · 57 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

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

  • Early 0% · 0
  • On time 100% · 30
  • 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=3
  • 100% F n=3
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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
08:49on time on time
08:53— —
08:56 / 09:02— —
09:04— —
09:10— —
09:13— —
09:18 / 09:21— —
09:25— —

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
Tue 17 NovUtrecht Overvecht 09:34Partial coverage0 min—
Mon 16 NovUtrecht Overvecht 09:34Partial coverage0 min—
Sun 15 NovUtrecht Overvecht 09:34Partial coverage0 min—
Sat 14 NovUtrecht Overvecht 09:34Partial coverage0 min—
Fri 13 NovUtrecht Overvecht 09:34Partial coverage0 min—
Thu 12 NovUtrecht Overvecht 09:34Partial coverage0 min—
Wed 11 NovUtrecht Overvecht 09:34Partial coverage0 min—
Tue 10 NovUtrecht Overvecht 09:34Partial coverage0 min—
Mon 9 NovUtrecht Overvecht 09:34Partial coverage0 min—
Sun 8 NovUtrecht Overvecht 09:34Partial coverage0 min—
Sat 7 NovUtrecht Overvecht 09:34Partial coverage0 min—
Fri 6 NovUtrecht Overvecht 09:34No data—
Thu 5 NovUtrecht Overvecht 09:34No data—
Wed 4 NovUtrecht Overvecht 09:34Partial coverage0 min—
Tue 3 NovUtrecht Overvecht 09:34No data—
Mon 2 NovUtrecht Overvecht 09:34No data—
Sun 1 NovUtrecht Overvecht 09:360 min—
Sat 31 OctUtrecht Overvecht 09:35Partial coverage0 min—
Fri 30 OctUtrecht Overvecht 09:35No data—
Thu 29 OctUtrecht Overvecht 09:35Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 09:35Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 09:35Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 09:35No data—
Sun 25 OctUtrecht Overvecht 09:36No data—
Sat 24 OctUtrecht Overvecht 09:35Partial coverage0 min—
Fri 23 OctUtrecht Overvecht 09:35No data—
Thu 22 OctUtrecht Overvecht 09:35No data—
Wed 21 OctUtrecht Overvecht 09:35No data—
Tue 20 OctUtrecht Overvecht 09:35Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 09:35Partial coverage0 min—