Train NS 4950 Utrecht Centraal – Almere Centrum

Utrecht Centraal 14:55 → Almere Centrum 15:38 Daily 0 h 43 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:55 from Utrecht Centraal · Sun 8 Nov

Next departure 14:55 today · Utrecht Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 7 full · 9 partial · 13 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 7 full · 14 partial · 67 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 Almere Centrum, 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

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

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

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
14:55on time on time
14:59≈ on time ≈ on time
15:09≈ on time ≈ on time
15:11 / 15:12≈ on time ≈ on time
15:17 / 15:20≈ on time ≈ on time
15:31≈ on time ≈ on time
15:35≈ on time ≈ on time
15:38on 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 NovAlmere Muziekwijk 15:49Partial coverage0 min—
Fri 6 NovAlmere Muziekwijk 15:49No data—
Thu 5 NovAlmere Muziekwijk 15:49Partial coverage0 min—
Wed 4 NovAlmere Muziekwijk 15:49Partial coverage0 min—
Tue 3 NovAlmere Muziekwijk 15:49Partial coverage0 min—
Mon 2 NovAlmere Muziekwijk 15:49No data—
Sun 1 NovAlmere Muziekwijk 15:500 min—
Sat 31 OctAlmere Muziekwijk 15:49Partial coverage0 min—
Fri 30 OctAlmere Muziekwijk 15:49Partial coverage0 min—
Thu 29 OctAlmere Muziekwijk 15:490 min—
Wed 28 OctAlmere Muziekwijk 15:500 min—
Tue 27 OctAlmere Muziekwijk 15:500 min—
Mon 26 OctAlmere Muziekwijk 15:49No data—
Sun 25 OctAlmere Muziekwijk 15:56No data—
Sat 24 OctAlmere Muziekwijk 15:49Partial coverage0 min—
Fri 23 OctAlmere Muziekwijk 15:50No data—
Thu 22 OctAlmere Muziekwijk 15:51No data—
Wed 21 OctAlmere Muziekwijk 15:49No data—
Tue 20 OctAlmere Muziekwijk 15:49No data—
Mon 19 OctAlmere Muziekwijk 15:50Partial coverage0 min—
Sun 18 OctHilversum Sportpark 15:250 min—
Sat 17 OctHilversum Sportpark 15:27No data—
Fri 16 OctAlmere Muziekwijk 15:50No data—
Thu 15 OctAlmere Muziekwijk 15:50No data—
Wed 14 OctAlmere Muziekwijk 15:49No data—
Tue 13 OctAlmere Muziekwijk 15:50No data—
Mon 12 OctAlmere Muziekwijk 15:490 min—
Sun 11 OctAlmere Muziekwijk 15:490 min—
Sat 10 OctAlmere Muziekwijk 15:51Partial coverage+2 min+2 min
Fri 9 OctAlmere Muziekwijk 15:50Partial coverage0 min—