Train NS 4974 Utrecht Centraal – Almere Centrum

Utrecht Centraal 20:54 → Almere Centrum 21:38 Daily 0 h 44 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 20:54 from Utrecht Centraal · Thu 5 Nov

Next departure 20:54 today · Utrecht Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 9 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 25 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: +2 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

  • Thu 8 Oct Max en route +5 min · last fix heading to — +3 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 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
20:54on time on time
20:58≈ on time ≈ on time
21:05≈ on time ≈ +1 min
21:09≈ on time ≈ +1 min
21:11 / 21:12≈ on time ≈ +1 min
21:17 / 21:20≈ on time ≈ +1 min
21:31≈ on time ≈ +2 min
21:35≈ on time ≈ +2 min
21:38on 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
Wed 4 Nov— 21:390 min—
Tue 3 Nov— 21:44No data—
Mon 2 Nov— 21:39+1 min+1 min
Sun 1 NovAlmere Muziekwijk 21:490 min—
Sat 31 OctAlmere Muziekwijk 21:500 min—
Fri 30 Oct— 21:39No data—
Wed 28 Oct— 21:560 min—
Tue 27 Oct— 21:50No data—
Mon 26 Oct— 21:39No data—
Sun 25 OctAlmere Muziekwijk 21:52No data—
Sat 24 OctAlmere Muziekwijk 21:490 min—
Fri 23 Oct— 21:400 min—
Thu 22 Oct— 21:400 min—
Wed 21 Oct— 21:390 min—
Tue 20 Oct— 21:390 min—
Mon 19 Oct— 21:42No data—
Sun 18 OctHilversum Sportpark 21:26+1 min+2 min
Sat 17 OctHilversum Sportpark 21:25No data—
Fri 16 Oct— 21:44+2 min+3 min
Thu 15 Oct— 21:410 min—
Wed 14 Oct— 21:43No data—
Tue 13 Oct— 21:400 min—
Mon 12 Oct— 21:39No data—
Sun 11 OctAlmere Muziekwijk 21:490 min—
Sat 10 OctAlmere Muziekwijk 21:490 min—
Fri 9 Oct— 21:44+2 min+4 min
Thu 8 Oct— 21:45+3 min+5 min
Wed 7 Oct— 21:40+1 min+1 min
Tue 6 Oct— 21:390 min—
Mon 5 Oct— 21:390 min—