Train NS 4959 Almere Centrum – Utrecht Centraal

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

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: today 16:51 from Almere Centrum · Mon 9 Nov

Next departure 16:51 today · Almere Centrum
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 13 full · 4 partial · 12 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 19 full · 4 partial · 65 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: +1 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 +4 min · last fix heading to Utrecht Overvecht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 50% W n=2
  • 100% T n=3
  • 100% F n=3
  • 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, 23 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
16:51on time on time
16:54≈ on time ≈ on time
16:58≈ on time ≈ on time
17:09 / 17:12≈ on time ≈ +1 min
17:17 / 17:18≈ on time ≈ +1 min
17:20≈ on time ≈ +2 min
17:31≈ on time ≈ +2 min
17:35on 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
Sun 8 NovUtrecht Overvecht 17:45Partial coverage+2 min+3 min
Sat 7 NovUtrecht Overvecht 17:44Partial coverage0 min—
Fri 6 NovUtrecht Overvecht 17:44+1 min+1 min
Thu 5 NovUtrecht Overvecht 17:44No data—
Wed 4 NovUtrecht Overvecht 17:440 min—
Tue 3 NovUtrecht Overvecht 17:44No data—
Mon 2 NovUtrecht Overvecht 17:39No data—
Sun 1 NovUtrecht Overvecht 17:45Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 17:450 min—
Fri 30 OctUtrecht Overvecht 17:45No data—
Thu 29 OctUtrecht Overvecht 17:450 min—
Wed 28 OctUtrecht Overvecht 17:45No data—
Tue 27 OctUtrecht Overvecht 17:45No data—
Mon 26 OctUtrecht Overvecht 17:45No data—
Sun 25 OctUtrecht Overvecht 17:45No data—
Sat 24 OctUtrecht Overvecht 17:48+3 min+3 min
Fri 23 OctUtrecht Overvecht 17:460 min—
Thu 22 OctUtrecht Overvecht 17:44No data—
Wed 21 OctUtrecht Overvecht 17:45No data—
Tue 20 OctUtrecht Overvecht 17:460 min—
Mon 19 OctUtrecht Overvecht 17:470 min—
Sun 18 OctUtrecht Overvecht 17:450 min—
Sat 17 OctUtrecht Overvecht 17:480 min—
Fri 16 OctUtrecht Overvecht 17:45No data—
Thu 15 OctUtrecht Overvecht 17:450 min—
Wed 14 OctUtrecht Overvecht 17:45No data—
Tue 13 OctUtrecht Overvecht 17:450 min—
Mon 12 OctUtrecht Overvecht 17:450 min—
Sun 11 OctUtrecht Overvecht 17:45Partial coverage0 min—
Sat 10 OctUtrecht Overvecht 17:450 min—