Train NS 4956 Utrecht Centraal – Almere Centrum

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

✓ Today’s run finished

Today, last fix heading to Almere Muziekwijk at 17:19 0 min

  1. Utrecht Centraal16:25
  2. Utrecht Overvecht16:29
  3. Hilversum Sportpark16:39
  4. Naarden-Bussum16:47
  5. Almere Poort17:01
  6. Almere Muziekwijk17:05
  7. Almere Centrum17:08

Next service: tomorrow 16:25 from Utrecht Centraal · Fri 6 Nov

Next departure 16:25 tomorrow · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 3 full · 15 partial · 12 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 3 full · 17 partial · 69 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

  • Mon 5 Oct Max en route +4 min · last fix heading to Almere Muziekwijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 100% F n=1
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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
16:25on time on time
16:29— —
16:39— —
16:41 / 16:42— —
16:47 / 16:50— —
17:01— —
17:05— —
17:08— —

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
Thu 5 NovAlmere Muziekwijk 17:19Partial coverage0 min—
Wed 4 NovAlmere Muziekwijk 17:19No data—
Tue 3 NovAlmere Muziekwijk 17:19No data—
Mon 2 NovAlmere Muziekwijk 17:19No data—
Sun 1 NovAlmere Muziekwijk 17:190 min—
Sat 31 OctAlmere Muziekwijk 17:19Partial coverage0 min+3 min
Fri 30 OctAlmere Muziekwijk 17:19No data—
Thu 29 OctAlmere Muziekwijk 17:19Partial coverage0 min—
Wed 28 OctAlmere Muziekwijk 17:19Partial coverage0 min—
Tue 27 OctAlmere Muziekwijk 17:20Partial coverage0 min—
Mon 26 OctAlmere Muziekwijk 17:19Partial coverage0 min—
Sun 25 OctAlmere Muziekwijk 17:19No data—
Sat 24 OctAlmere Muziekwijk 17:20Partial coverage0 min—
Fri 23 OctAlmere Muziekwijk 17:23No data—
Thu 22 OctAlmere Muziekwijk 17:19No data—
Wed 21 OctAlmere Muziekwijk 17:17Partial coverage0 min—
Tue 20 OctAlmere Muziekwijk 17:24No data—
Mon 19 OctAlmere Muziekwijk 17:19Partial coverage0 min—
Sun 18 OctHilversum Sportpark 16:55+1 min—
Sat 17 OctHilversum Sportpark 16:55No data—
Fri 16 OctAlmere Muziekwijk 17:20No data—
Thu 15 OctAlmere Muziekwijk 17:17Partial coverage0 min—
Wed 14 OctAlmere Muziekwijk 17:19No data—
Tue 13 OctAlmere Muziekwijk 17:21No data—
Mon 12 OctAlmere Muziekwijk 17:19Partial coverage0 min—
Sun 11 OctAlmere Muziekwijk 17:190 min—
Sat 10 OctAlmere Muziekwijk 17:22Partial coverage+3 min+3 min
Fri 9 OctAlmere Muziekwijk 17:20Partial coverage0 min—
Thu 8 OctAlmere Muziekwijk 17:19Partial coverage0 min—
Wed 7 OctAlmere Muziekwijk 17:19Partial coverage0 min—