Train NS 4961 Almere Centrum – Utrecht Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 17:21 from Almere Centrum · Sun 8 Nov

Next departure 17:21 today · Almere Centrum
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 14 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 17 full · 3 partial · 68 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=1
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

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