Train NS 4978 Utrecht Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 21:54 from Utrecht Centraal · Thu 19 Nov

Next departure 21:54 today · Utrecht Centraal
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 6 no data
On-time · 90 days
92%
35/38 runs under 3 min
RT coverage: 38 full · 0 partial · 19 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: +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 17 Nov Max en route +9 min · last fix heading to — +8 min
  • Sat 10 Oct Max en route +11 min · last fix heading to Hollandsche Rading +8 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Almere Muziekwijk +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 35
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 83% T n=6
  • 100% W n=7
  • 100% T n=6
  • 100% F n=5
  • 67% S n=3
  • 80% S n=5

Stops and timetable

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

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