Train NS 4936 Utrecht Centraal – Almere Centrum

Utrecht Centraal 11:25 → Almere Centrum 12:08 Daily 0 h 43 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 11:25 from Utrecht Centraal · Wed 18 Nov

Next departure 11:25 today · Utrecht Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 1 full · 19 partial · 8 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 3 full · 27 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
11:25on time on time
11:29— —
11:39— —
11:41 / 11:42— —
11:47 / 11:50— —
12:01— —
12:05— —
12:08— —

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