Train NS 4971 Almere Centrum – Utrecht Centraal

Almere Centrum 19:51 → Utrecht Centraal 20:35 Daily 0 h 44 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 19:51 from Almere Centrum · Sun 8 Nov

Next departure 19:51 today · Almere Centrum
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 19 full · 2 partial · 7 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 24 full · 2 partial · 28 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: 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

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

  • Early 0% · 0
  • On time 100% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 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, 26 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
19:51on time on time
19:54≈ on time ≈ on time
19:58≈ on time ≈ on time
20:09 / 20:12≈ on time ≈ on time
20:17 / 20:18≈ on time ≈ on time
20:20≈ on time ≈ on time
20:31≈ on time ≈ on time
20:35on time +1 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
Sat 7 NovUtrecht Overvecht 20:44Partial coverage+1 min—
Fri 6 Nov— 20:340 min—
Thu 5 Nov— 20:350 min—
Wed 4 Nov— 20:340 min—
Mon 2 Nov— 20:370 min—
Sun 1 NovUtrecht Overvecht 20:440 min—
Sat 31 OctUtrecht Overvecht 20:450 min—
Fri 30 Oct— 20:37No data—
Thu 29 Oct— 20:360 min+1 min
Wed 28 Oct— 20:440 min—
Tue 27 Oct— 20:390 min—
Mon 26 Oct— 20:39No data—
Sun 25 OctUtrecht Overvecht 20:45No data—
Sat 24 OctUtrecht Overvecht 20:45Partial coverage0 min—
Fri 23 Oct— 20:360 min—
Thu 22 Oct— 20:370 min—
Wed 21 Oct— 03:250 min—
Tue 20 Oct— 20:390 min—
Mon 19 Oct— 20:39No data—
Sun 18 OctUtrecht Overvecht 20:450 min—
Sat 17 OctUtrecht Overvecht 20:45No data—
Fri 16 OctAlmere Centrum 20:360 min—
Thu 15 Oct— 20:390 min—
Wed 14 Oct— 20:370 min—
Tue 13 Oct— 20:37No data—
Mon 12 Oct— 20:37No data—
Sun 11 OctUtrecht Overvecht 20:450 min—
Sat 10 OctUtrecht Overvecht 20:47+3 min+3 min
Fri 9 Oct— 20:360 min—
Thu 8 Oct— 03:250 min+3 min