Train NS 4964 Utrecht Centraal – Almere Centrum

Utrecht Centraal 18:25 → Almere Centrum 19:08 Daily 0 h 43 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 19:12 No data

  1. Utrecht Centraal18:25
  2. Utrecht Overvecht18:29
  3. Hilversum Sportpark18:39
  4. Naarden-Bussum18:47
  5. Almere Poort19:01
  6. Almere Muziekwijk19:05
  7. Almere Centrum19:08

Next service: tomorrow 18:25 from Utrecht Centraal · Thu 5 Nov

Next departure 18:25 tomorrow · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 11 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 11 full · 8 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
18:25on time on time
18:29≈ on time ≈ on time
18:39≈ on time ≈ on time
18:41 / 18:42≈ on time ≈ on time
18:47 / 18:50≈ on time ≈ on time
19:01≈ on time ≈ on time
19:05≈ on time ≈ on time
19:08on time +1 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 4 Nov— 19:12No data—
Mon 2 NovUtrecht Overvecht 19:09Partial coverage0 min—
Sun 1 NovAlmere Muziekwijk 19:190 min—
Sat 31 OctAlmere Muziekwijk 19:20Partial coverage0 min—
Fri 30 OctNaarden-Bussum 19:09No data—
Thu 29 Oct— 19:090 min—
Wed 28 Oct— 19:080 min—
Tue 27 Oct— 19:10No data—
Mon 26 Oct— 19:10No data—
Sun 25 OctAlmere Muziekwijk 19:20No data—
Sat 24 OctAlmere Muziekwijk 19:23Partial coverage0 min—
Fri 23 OctAlmere Muziekwijk 19:15Partial coverage0 min—
Thu 22 OctHilversum 19:19No data—
Wed 21 OctHilversum Sportpark 19:10No data—
Tue 20 OctHilversum 19:09Partial coverage0 min—
Mon 19 OctHilversum 19:100 min—
Sun 18 OctHilversum Sportpark 18:550 min—
Sat 17 OctHilversum Sportpark 18:54No data—
Fri 16 OctAlmere Muziekwijk 19:19Partial coverage0 min—
Thu 15 OctUtrecht Overvecht 19:12No data—
Wed 14 OctAlmere Muziekwijk 19:19Partial coverage0 min—
Tue 13 OctHilversum Sportpark 19:09No data—
Mon 12 OctHilversum 19:09No data—
Sun 11 OctAlmere Muziekwijk 19:190 min—
Sat 10 OctAlmere Muziekwijk 19:190 min—
Fri 9 OctUtrecht Overvecht 19:14Partial coverage+2 min+2 min
Thu 8 Oct— 19:090 min—
Wed 7 Oct— 19:090 min—
Tue 6 Oct— 19:10+1 min+1 min
Mon 5 Oct— 19:10+1 min+1 min