Train NS 4977 Almere Centrum – Utrecht Centraal

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 21:21 from Almere Centrum · Tue 17 Nov

Next departure 21:21 today · Almere Centrum
On-time · 30 days
81%
13/16 runs under 3 min
RT coverage: 15 full · 1 partial · 10 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 26 full · 1 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Utrecht Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 7 Oct Max en route +10 min · last fix heading to — +10 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Utrecht Overvecht +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to — +5 min
  • Mon 9 Nov Max en route +4 min · last fix heading to — +4 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 85% · 23
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 67% W n=3
  • 50% T n=2
  • 100% F n=5
  • 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, 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
21:21on time on time
21:24≈ on time ≈ on time
21:28≈ on time ≈ +1 min
21:39 / 21:41≈ on time ≈ +2 min
21:46 / 21:47≈ on time ≈ +2 min
21:50≈ on time ≈ +3 min
21:54≈ on time ≈ +3 min
22:02≈ on time ≈ +4 min
22:06on time +4 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 NovNaarden-Bussum 22:08Partial coverage0 min—
Sun 15 NovUtrecht Overvecht 22:19+5 min+5 min
Sat 14 NovUtrecht Overvecht 22:14+1 min—
Fri 13 Nov— 22:070 min—
Thu 12 Nov— 22:14+5 min+5 min
Wed 11 Nov— 22:070 min—
Tue 10 Nov— 22:080 min+3 min
Mon 9 Nov— 22:12+4 min+4 min
Sun 8 NovUtrecht Overvecht 22:170 min+1 min
Sat 7 NovUtrecht Overvecht 22:140 min—
Fri 6 Nov— 22:09+1 min+1 min
Thu 5 Nov— 22:08No data—
Wed 4 Nov— 22:080 min—
Sun 1 NovUtrecht Overvecht 22:140 min—
Sat 31 OctUtrecht Overvecht 22:16No data—
Fri 30 Oct— 22:11No data—
Wed 28 Oct— 22:07No data—
Tue 27 Oct— 22:08No data—
Mon 26 Oct— 22:10No data—
Sun 25 OctUtrecht Overvecht 22:16No data—
Sat 24 OctUtrecht Overvecht 22:180 min—
Fri 23 Oct— 22:080 min—
Thu 22 Oct— 22:14No data—
Wed 21 Oct— 22:16No data—
Tue 20 Oct— 22:08No data—
Mon 19 Oct— 22:080 min—
Sun 18 OctUtrecht Overvecht 22:150 min—
Sat 17 OctUtrecht Overvecht 22:15No data—
Fri 16 Oct— 22:10+1 min+1 min
Thu 15 Oct— 22:09No data—