Train NS 4952 Utrecht Centraal – Almere Centrum

Utrecht Centraal 15:25 → Almere Centrum 16:08 Daily 0 h 43 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 15:25 from Utrecht Centraal · Tue 17 Nov

Next departure 15:25 today · Utrecht Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 7 full · 16 partial · 6 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 8 full · 25 partial · 55 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 Almere Centrum, in minutes. One bar per run.

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

Worst days

  • Wed 7 Oct Max en route +3 min · last fix heading to Almere Muziekwijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 75% W n=4
  • 100% T n=3
  • 100% F n=5
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 33 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
15:25on time on time
15:29≈ on time ≈ on time
15:39≈ on time ≈ on time
15:41 / 15:42≈ on time ≈ on time
15:47 / 15:50≈ on time ≈ on time
16:01≈ on time ≈ on time
16:05≈ on time ≈ on time
16:08on 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
Mon 16 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Sun 15 NovAlmere Muziekwijk 16:19+1 min—
Sat 14 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Fri 13 NovAlmere Muziekwijk 16:22Partial coverage+3 min+3 min
Thu 12 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Wed 11 NovAlmere Muziekwijk 16:19Partial coverage+1 min+1 min
Tue 10 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Mon 9 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Sun 8 NovAlmere Muziekwijk 16:200 min—
Sat 7 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Fri 6 NovAlmere Muziekwijk 16:19No data—
Thu 5 NovAlmere Muziekwijk 16:20No data—
Wed 4 NovAlmere Muziekwijk 16:19Partial coverage0 min—
Tue 3 NovAlmere Muziekwijk 16:19No data—
Mon 2 NovUtrecht Centraal 17:090 min—
Sun 1 NovAlmere Muziekwijk 16:200 min—
Sat 31 OctAlmere Muziekwijk 16:20Partial coverage0 min—
Fri 30 OctAlmere Muziekwijk 16:19Partial coverage0 min—
Thu 29 OctAlmere Muziekwijk 16:19Partial coverage0 min—
Wed 28 OctAlmere Muziekwijk 16:190 min—
Tue 27 OctAlmere Muziekwijk 16:200 min—
Mon 26 OctAlmere Muziekwijk 16:19Partial coverage0 min—
Sun 25 OctAlmere Muziekwijk 16:20No data—
Sat 24 OctAlmere Muziekwijk 16:19Partial coverage0 min—
Fri 23 OctAlmere Muziekwijk 16:19Partial coverage0 min—
Thu 22 OctAlmere Muziekwijk 16:20No data—
Wed 21 OctAlmere Muziekwijk 16:21No data—
Tue 20 OctAlmere Muziekwijk 16:19Partial coverage0 min—
Mon 19 OctAlmere Muziekwijk 16:220 min—
Sun 18 OctHilversum Sportpark 15:540 min—