Train NS 4967 Almere Centrum – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 19:37 +1 min

  1. Almere Centrum18:51
  2. Almere Muziekwijk18:54
  3. Almere Poort18:58
  4. Hilversum19:17
  5. Hilversum Sportpark19:20
  6. Utrecht Overvecht19:31
  7. Utrecht Centraal19:35

Next service: tomorrow 18:51 from Almere Centrum · Wed 18 Nov

Next departure 18:51 tomorrow · Almere Centrum
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 11 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 23 full · 6 partial · 34 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: +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

  • Sun 15 Nov Max en route +6 min · last fix heading to Utrecht Overvecht +6 min
  • Thu 29 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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:51on time on time
18:54≈ on time ≈ on time
18:58≈ on time ≈ on time
19:09 / 19:12≈ on time ≈ +1 min
19:17 / 19:18≈ on time ≈ +1 min
19:20≈ on time ≈ +2 min
19:31≈ on time ≈ +2 min
19: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
Tue 17 Nov— 19:37+1 min+2 min
Mon 16 Nov— 19:370 min+1 min
Sun 15 NovUtrecht Overvecht 19:49+6 min+6 min
Sat 14 NovUtrecht Overvecht 19:44Partial coverage0 min—
Fri 13 NovAlmere Muziekwijk 19:39Partial coverage+2 min+3 min
Thu 12 Nov— 19:380 min—
Wed 11 Nov— 19:38+2 min+3 min
Tue 10 Nov— 19:39+3 min+3 min
Mon 9 Nov— 19:380 min—
Sun 8 NovUtrecht Overvecht 19:440 min—
Sat 7 NovUtrecht Overvecht 19:44Partial coverage0 min—
Fri 6 Nov— 19:340 min—
Thu 5 Nov— 19:34No data—
Wed 4 Nov— 19:34No data—
Tue 3 Nov— 19:37No data—
Mon 2 Nov— 19:340 min—
Sun 1 NovUtrecht Overvecht 19:440 min—
Sat 31 OctUtrecht Overvecht 19:45Partial coverage0 min—
Fri 30 OctAlmere Muziekwijk 19:36No data—
Thu 29 Oct— 19:38+3 min+3 min
Wed 28 Oct— 19:38No data—
Tue 27 Oct— 19:370 min—
Mon 26 Oct— 19:37No data—
Sun 25 OctUtrecht Overvecht 19:45No data—
Sat 24 OctUtrecht Overvecht 19:48No data—
Fri 23 OctHilversum Sportpark 19:37Partial coverage0 min+2 min
Thu 22 Oct— 19:37No data—
Wed 21 Oct— 19:39No data—
Tue 20 Oct— 19:37No data—
Mon 19 Oct— 19:360 min—