Train NS 4965 Almere Centrum – Utrecht Centraal

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

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

Next departure 18:21 today · Almere Centrum
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 8 full · 11 partial · 10 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 15 full · 13 partial · 41 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 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

  • Thu 8 Oct Max en route +40 min · last fix heading to — +31 min
  • Tue 10 Nov Max en route +7 min · last fix heading to Almere Centrum +6 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Almere Centrum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 4% · 1

On-time by weekday

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

Stops and timetable

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

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