Train NS 4957 Almere Centrum – Utrecht Centraal

Almere Centrum 16:21 → Utrecht Centraal 17:05 Daily 0 h 44 min · 8 stops NS (Nederlandse Spoorwegen)

Running now · updated 16:20

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 17:05 · 3 km/h

  1. Almere Centrum16:21
  2. Almere Muziekwijk16:24
  3. Almere Poort16:28
  4. Hilversum16:47
  5. Hilversum Sportpark16:50
  6. Utrecht Overvecht17:01
  7. Utrecht Centraal17:05

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 8 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 33 full · 3 partial · 53 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 Utrecht Centraal, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=4
  • 100% T n=3
  • 100% F n=6
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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 10Today
16:21on time on time
16:24≈ on time ≈ on time
16:28≈ on time ≈ on time
16:39 / 16:42≈ on time ≈ +1 min
16:47 / 16:48≈ on time ≈ +1 min
16:50≈ on time ≈ +1 min
17:01≈ on time ≈ +1 min
17:05on 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 NovAlmere Centrum 16:19Partial coverage0 min—
Tue 17 NovUtrecht Overvecht 17:140 min+1 min
Mon 16 NovUtrecht Overvecht 17:150 min—
Sun 15 NovUtrecht Overvecht 17:14+2 min+5 min
Sat 14 NovUtrecht Overvecht 17:18+3 min+3 min
Fri 13 NovUtrecht Overvecht 17:14+1 min—
Thu 12 NovUtrecht Overvecht 17:14+2 min+2 min
Wed 11 NovUtrecht Overvecht 17:14+1 min+2 min
Tue 10 NovUtrecht Overvecht 17:140 min—
Mon 9 NovUtrecht Overvecht 17:140 min—
Sun 8 NovUtrecht Overvecht 17:150 min—
Sat 7 NovUtrecht Overvecht 17:14+1 min—
Fri 6 NovUtrecht Overvecht 17:140 min—
Thu 5 NovUtrecht Overvecht 17:14No data—
Wed 4 NovUtrecht Overvecht 17:14No data—
Tue 3 NovUtrecht Overvecht 17:14No data—
Mon 2 NovUtrecht Overvecht 17:140 min—
Sun 1 NovUtrecht Overvecht 17:15+1 min—
Sat 31 OctUtrecht Overvecht 17:150 min—
Fri 30 OctUtrecht Overvecht 17:150 min—
Thu 29 OctUtrecht Overvecht 17:15No data—
Wed 28 OctUtrecht Overvecht 17:15Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 17:15Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 17:15No data—
Sun 25 OctUtrecht Overvecht 17:15No data—
Sat 24 OctUtrecht Overvecht 17:150 min—
Fri 23 OctUtrecht Overvecht 17:160 min—
Thu 22 OctUtrecht Overvecht 17:16No data—
Wed 21 OctUtrecht Overvecht 17:17No data—
Tue 20 OctUtrecht Overvecht 17:210 min—