Train NS 4980 Utrecht Centraal – Almere Centrum

Utrecht Centraal 22:24 → Almere Centrum 23:08 Daily 0 h 44 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +2 min

Next service: today 22:24 from Utrecht Centraal · Tue 17 Nov

Next departure 22:24 today · Utrecht Centraal
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 11 full · 5 partial · 12 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 21 full · 6 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 11 Oct Max en route +16 min · last fix heading to Almere Muziekwijk +16 min
  • Mon 2 Nov Max en route +9 min · last fix heading to — +9 min
  • Mon 9 Nov Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 7% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=5
  • 100% 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, 27 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
22:24on time on time
22:28≈ on time ≈ on time
22:35≈ on time ≈ +1 min
22:39≈ on time ≈ +1 min
22:41 / 22:42≈ on time ≈ +1 min
22:47 / 22:50≈ on time ≈ +1 min
23:01≈ on time ≈ +2 min
23:05≈ on time ≈ +2 min
23:08on 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
Mon 16 Nov— 23:14+2 min+3 min
Sun 15 NovAlmere Muziekwijk 23:19Partial coverage+1 min+1 min
Sat 14 NovAlmere Poort 23:14Partial coverage0 min—
Fri 13 Nov— 23:090 min—
Thu 12 Nov— 23:12+2 min+4 min
Wed 11 Nov— 23:090 min—
Tue 10 Nov— 23:090 min—
Mon 9 Nov— 23:18+5 min+7 min
Sun 8 NovAlmere Muziekwijk 23:19Partial coverage0 min—
Sat 7 NovAlmere Muziekwijk 23:19Partial coverage0 min—
Fri 6 Nov— 23:090 min—
Thu 5 Nov— 23:44No data—
Wed 4 Nov— 23:090 min—
Mon 2 Nov— 23:18+9 min+9 min
Sun 1 NovAlmere Muziekwijk 23:19Partial coverage0 min—
Sat 31 OctAlmere Muziekwijk 23:19No data—
Fri 30 Oct— 23:09No data—
Thu 29 Oct— 23:10+1 min—
Wed 28 Oct— 23:09No data—
Tue 27 Oct— 23:11No data—
Mon 26 Oct— 23:10No data—
Sun 25 OctAlmere Muziekwijk 23:19No data—
Sat 24 OctHilversum Sportpark 23:13No data—
Fri 23 Oct— 23:100 min—
Thu 22 Oct— 23:10No data—
Wed 21 Oct— 23:12No data—
Tue 20 Oct— 23:09No data—
Mon 19 Oct— 23:09No data—
Sun 18 OctHilversum Sportpark 22:560 min—
Sat 17 OctHilversum Sportpark 22:55No data—