Train NS 4934 Utrecht Centraal – Almere Centrum

Utrecht Centraal 10:55 → Almere Centrum 11:38 Daily 0 h 43 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 10:55 from Utrecht Centraal · Sat 7 Nov

Next departure 10:55 today · Utrecht Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 8 full · 9 partial · 11 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 8 full · 12 partial · 67 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 Almere Centrum, 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=2
  • 100% T n=2
  • 100% W n=4
  • 100% T n=4
  • 100% F n=2
  • 100% S n=4
  • 100% S n=2

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
10:55on time on time
10:59≈ on time ≈ on time
11:09≈ on time ≈ on time
11:11 / 11:12≈ on time ≈ on time
11:17 / 11:20≈ on time ≈ on time
11:31≈ on time ≈ on time
11:35≈ on time ≈ on time
11:38on time on time

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
Fri 6 NovAlmere Muziekwijk 11:49No data—
Thu 5 NovAlmere Muziekwijk 11:49Partial coverage0 min—
Wed 4 NovAlmere Muziekwijk 11:49+1 min+4 min
Tue 3 NovAlmere Muziekwijk 11:49No data—
Mon 2 NovAlmere Muziekwijk 11:49No data—
Sat 31 OctAlmere Muziekwijk 11:49Partial coverage0 min—
Fri 30 OctAlmere Muziekwijk 11:49No data—
Thu 29 OctAlmere Muziekwijk 11:490 min—
Wed 28 OctAlmere Muziekwijk 11:500 min—
Tue 27 OctAlmere Muziekwijk 11:490 min—
Mon 26 OctAlmere Muziekwijk 11:490 min—
Sun 25 OctAlmere Muziekwijk 11:49No data—
Sat 24 OctAlmere Muziekwijk 11:50Partial coverage+1 min+1 min
Fri 23 OctAlmere Muziekwijk 11:49Partial coverage0 min—
Thu 22 OctAlmere Muziekwijk 11:49No data—
Wed 21 OctAlmere Muziekwijk 11:49Partial coverage0 min—
Tue 20 OctAlmere Muziekwijk 11:49No data—
Mon 19 OctAlmere Muziekwijk 11:49Partial coverage0 min—
Sun 18 OctHilversum Sportpark 11:240 min—
Sat 17 OctHilversum Sportpark 11:250 min—
Fri 16 OctAlmere Muziekwijk 11:51No data—
Thu 15 OctAlmere Muziekwijk 11:490 min—
Wed 14 OctAlmere Muziekwijk 11:51No data—
Tue 13 OctAlmere Muziekwijk 11:49No data—
Mon 12 OctAlmere Muziekwijk 11:49No data—
Sun 11 OctAlmere Muziekwijk 11:50Partial coverage+1 min—
Sat 10 OctAlmere Muziekwijk 11:49Partial coverage0 min—
Fri 9 OctAlmere Muziekwijk 11:50Partial coverage+1 min+1 min
Thu 8 OctAlmere Muziekwijk 11:49Partial coverage0 min—
Wed 7 OctUtrecht Overvecht 12:01Partial coverage0 min—