Train NS 4966 Utrecht Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:55 from Utrecht Centraal · Sat 7 Nov

Next departure 18:55 today · Utrecht Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 14 full · 4 partial · 10 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 17 full · 4 partial · 38 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

  • Tue 6 Oct Max en route +9 min · last fix heading to — +9 min
  • Wed 4 Nov Max en route +7 min · last fix heading to — +7 min

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 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 50% T n=2
  • 67% W n=3
  • 100% T n=1
  • 100% F n=4
  • 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, 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
18:55on time on time
18:59≈ on time ≈ +1 min
19:09≈ on time ≈ +2 min
19:11 / 19:12≈ on time ≈ +2 min
19:17 / 19:20≈ on time ≈ +2 min
19:31≈ on time ≈ +3 min
19:35≈ on time ≈ +3 min
19:38on time +3 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
Fri 6 Nov— 19:390 min—
Thu 5 Nov— 19:39No data—
Wed 4 Nov— 19:49+7 min+7 min
Tue 3 Nov— 19:39No data—
Mon 2 Nov— 19:48+1 min+1 min
Sun 1 NovAlmere Muziekwijk 19:490 min—
Sat 31 OctAlmere Muziekwijk 19:50Partial coverage+1 min—
Fri 30 Oct— 19:48No data—
Wed 28 Oct— 19:390 min—
Tue 27 Oct— 19:40No data—
Mon 26 Oct— 19:390 min—
Sun 25 OctAlmere Muziekwijk 19:51No data—
Sat 24 OctAlmere Muziekwijk 19:49Partial coverage0 min—
Fri 23 OctNaarden-Bussum 19:39Partial coverage0 min—
Thu 22 Oct— 19:48No data—
Wed 21 Oct— 19:40No data—
Tue 20 Oct— 19:390 min—
Mon 19 Oct— 20:040 min—
Sun 18 OctHilversum Sportpark 19:260 min+1 min
Sat 17 OctHilversum Sportpark 19:27No data—
Fri 16 OctAlmere Muziekwijk 19:490 min—
Thu 15 Oct— 19:42No data—
Wed 14 OctAlmere Muziekwijk 19:490 min—
Tue 13 Oct— 19:39No data—
Mon 12 Oct— 19:390 min—
Sun 11 OctAlmere Muziekwijk 19:490 min—
Sat 10 OctAlmere Muziekwijk 19:49Partial coverage0 min—
Fri 9 Oct— 19:40+1 min+2 min
Thu 8 Oct— 19:000 min—
Tue 6 Oct— 19:48+9 min+9 min