Train NS 4963 Almere Centrum – Utrecht Centraal

Almere Centrum 17:51 → Utrecht Centraal 18:35 Daily 0 h 44 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +2 min

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

Next departure 17:51 today · Almere Centrum
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 16 full · 3 partial · 10 no data
On-time · 90 days
89%
25/28 runs under 3 min
RT coverage: 24 full · 4 partial · 60 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: +6 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

  • Tue 10 Nov Max en route +9 min · last fix heading to Hilversum Sportpark +9 min
  • Sun 15 Nov Max en route +7 min · last fix heading to Utrecht Overvecht +6 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Hilversum Sportpark +5 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 89% · 25
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
17:51on time on time
17:54≈ on time ≈ on time
17:58≈ on time ≈ on time
18:09 / 18:12≈ on time ≈ +1 min
18:17 / 18:18≈ on time ≈ +1 min
18:20≈ on time ≈ +2 min
18:31≈ on time ≈ +2 min
18:35on 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 NovHilversum Sportpark 18:40+2 min+3 min
Sun 15 NovUtrecht Overvecht 18:49Partial coverage+6 min+7 min
Sat 14 NovUtrecht Overvecht 18:44+1 min+2 min
Fri 13 NovUtrecht Overvecht 18:44+2 min+2 min
Thu 12 NovHilversum Sportpark 18:42+5 min+6 min
Wed 11 NovNaarden-Bussum 18:38+2 min+3 min
Tue 10 NovHilversum Sportpark 18:53+9 min+9 min
Mon 9 NovNaarden-Bussum 18:370 min—
Sun 8 NovUtrecht Overvecht 18:45Partial coverage0 min—
Sat 7 NovUtrecht Overvecht 18:440 min—
Fri 6 NovUtrecht Overvecht 18:44+1 min—
Thu 5 NovNaarden-Bussum 18:37No data—
Wed 4 NovNaarden-Bussum 18:37No data—
Tue 3 NovNaarden-Bussum 18:39No data—
Mon 2 NovAlmere Poort 18:12No data—
Sun 1 NovUtrecht Overvecht 18:44Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 18:450 min+1 min
Fri 30 OctUtrecht Overvecht 18:45No data—
Thu 29 OctAlmere Poort 18:370 min—
Wed 28 OctNaarden-Bussum 18:38+1 min+1 min
Tue 27 OctAlmere Poort 18:43No data—
Mon 26 OctAlmere Poort 18:360 min—
Sun 25 OctUtrecht Overvecht 18:45No data—
Sat 24 OctUtrecht Overvecht 18:45No data—
Fri 23 OctUtrecht Overvecht 18:45No data—
Thu 22 OctUtrecht Overvecht 18:450 min—
Wed 21 OctUtrecht Overvecht 18:45No data—
Tue 20 OctUtrecht Overvecht 18:450 min—
Mon 19 OctUtrecht Overvecht 18:450 min—
Sun 18 OctUtrecht Overvecht 18:450 min—