Train NS 4970 Utrecht Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Tuesday 17 November +2 min

Next service: today 19:54 from Utrecht Centraal · Wed 18 Nov

Next departure 19:54 today · Utrecht Centraal
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 9 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 30 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 9 Oct Max en route +10 min · last fix heading to — +10 min
  • Wed 4 Nov Max en route +8 min · last fix heading to — +8 min
  • Sun 15 Nov Max en route +7 min · last fix heading to Almere Muziekwijk +5 min
  • Wed 11 Nov Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 26
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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:54on time on time
19:58≈ on time ≈ +1 min
20:05≈ on time ≈ +1 min
20:09≈ on time ≈ +2 min
20:11 / 20:12≈ on time ≈ +2 min
20:17 / 20:20≈ on time ≈ +3 min
20:31≈ on time ≈ +4 min
20:35≈ on time ≈ +5 min
20:38on time +5 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
Tue 17 Nov— 20:43+2 min+3 min
Mon 16 Nov— 20:390 min—
Sun 15 NovAlmere Muziekwijk 20:54+5 min+7 min
Sat 14 NovAlmere Muziekwijk 20:490 min—
Fri 13 Nov— 20:39+1 min—
Thu 12 Nov— 20:44+3 min+6 min
Wed 11 Nov— 20:48+5 min+6 min
Tue 10 Nov— 20:390 min—
Mon 9 Nov— 20:390 min—
Sun 8 NovAlmere Muziekwijk 20:490 min—
Sat 7 NovAlmere Muziekwijk 20:490 min—
Fri 6 Nov— 20:490 min—
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:49+8 min+8 min
Mon 2 Nov— 20:39No data—
Sun 1 NovAlmere Muziekwijk 20:490 min—
Sat 31 OctAlmere Muziekwijk 20:490 min—
Thu 29 Oct— 20:390 min—
Wed 28 Oct— 20:48No data—
Tue 27 Oct— 20:400 min—
Mon 26 Oct— 20:39No data—
Sun 25 OctAlmere Muziekwijk 20:51No data—
Sat 24 OctAlmere Muziekwijk 20:54No data—
Fri 23 Oct— 20:390 min—
Thu 22 Oct— 20:40No data—
Wed 21 Oct— 20:44No data—
Tue 20 Oct— 20:46No data—
Mon 19 Oct— 20:390 min—
Sun 18 OctHilversum Sportpark 20:250 min—
Sat 17 OctHilversum Sportpark 20:28No data—