Train NS 5518 Baarn – Utrecht Centraal

Baarn 07:19 → Utrecht Centraal 07:55 Mon, Tue, Wed, Thu, Fri, Sat 0 h 36 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Utrecht Overvecht at 08:05 0 min

  1. Baarn07:19
  2. Soestdijk07:23
  3. Soest07:26
  4. Den Dolder07:40
  5. Bilthoven07:43
  6. Utrecht Overvecht07:48
  7. Utrecht Centraal07:55

Next service: Monday 07:19 from Baarn · Mon 9 Nov

Full trip card
Next departure 07:19 Monday · Baarn
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 6 full · 13 partial · 7 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 7 full · 15 partial · 53 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

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

  • Early 0% · 0
  • On time 100% · 22
  • 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=4
  • 100% W n=4
  • 100% T n=2
  • 100% F n=4
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
Baarn
07:19on time on time
Soestdijk
07:23≈ on time ≈ on time
Soest
07:26 / 07:32≈ on time ≈ on time
Soest Zuid
07:34≈ on time ≈ on time
Den Dolder
07:40≈ on time ≈ on time
Bilthoven
07:43≈ on time ≈ on time
Utrecht Overvecht
07:48 / 07:51≈ on time ≈ on time
Utrecht Centraal
07:55on 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
Sat 7 NovUtrecht Overvecht 08:05Partial coverage0 min—
Fri 6 NovUtrecht Overvecht 08:04No data—
Thu 5 NovUtrecht Overvecht 08:04No data—
Wed 4 NovUtrecht Overvecht 08:04Partial coverage0 min—
Tue 3 NovUtrecht Overvecht 08:040 min—
Mon 2 NovUtrecht Overvecht 08:040 min—
Sat 31 OctUtrecht Overvecht 08:05Partial coverage0 min—
Fri 30 OctUtrecht Overvecht 08:05Partial coverage0 min—
Thu 29 OctUtrecht Overvecht 08:05Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 08:05Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 08:050 min—
Mon 26 OctUtrecht Overvecht 08:050 min—
Sat 24 OctUtrecht Overvecht 08:05Partial coverage0 min—
Fri 23 OctUtrecht Overvecht 08:05Partial coverage0 min—
Thu 22 OctUtrecht Overvecht 08:05No data—
Wed 21 OctUtrecht Overvecht 08:05No data—
Tue 20 OctUtrecht Overvecht 08:050 min—
Mon 19 OctUtrecht Overvecht 08:05Partial coverage0 min—
Sat 17 OctUtrecht Overvecht 08:050 min—
Fri 16 OctUtrecht Overvecht 08:05Partial coverage0 min—
Thu 15 OctUtrecht Overvecht 08:05No data—
Wed 14 OctUtrecht Overvecht 08:05Partial coverage0 min—
Tue 13 OctUtrecht Overvecht 08:05No data—
Mon 12 OctUtrecht Overvecht 08:05No data—
Sat 10 OctUtrecht Overvecht 08:05Partial coverage0 min—
Fri 9 OctUtrecht Overvecht 08:05Partial coverage0 min—
Thu 8 OctUtrecht Overvecht 08:06Partial coverage+1 min+2 min
Wed 7 OctUtrecht Overvecht 08:05Partial coverage+1 min+1 min
Tue 6 OctUtrecht Overvecht 08:050 min—
Mon 5 OctUtrecht Overvecht 08:06No data—