Train NS 4976 Utrecht Centraal – Almere Centrum

Utrecht Centraal 21:24 → Almere Centrum 22:08 Daily 0 h 44 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 21:24 from Utrecht Centraal · Tue 17 Nov

Next departure 21:24 today · Utrecht Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 11 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 21 full · 7 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 4 Nov Max en route +11 min · last fix heading to — +11 min
  • Mon 2 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
21:24on time on time
21:28≈ on time ≈ on time
21:35≈ on time ≈ +1 min
21:39≈ on time ≈ +1 min
21:41 / 21:42≈ on time ≈ +1 min
21:47 / 21:50≈ on time ≈ +1 min
22:01≈ on time ≈ +2 min
22:05≈ on time ≈ +2 min
22:08on time +2 min

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