Train NS 4940 Utrecht Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 12:25 from Utrecht Centraal · Tue 17 Nov

Next departure 12:25 today · Utrecht Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 1 full · 18 partial · 9 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 2 full · 25 partial · 60 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 Almere Centrum, 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 +8 min · last fix heading to Almere Muziekwijk +8 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 75% W n=4
  • 100% T n=2
  • 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, 27 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
12:25on time on time
12:29— —
12:39— —
12:41 / 12:42— —
12:47 / 12:50— —
13:01— —
13:05— —
13: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
Mon 16 NovAlmere Muziekwijk 13:20Partial coverage+1 min+2 min
Sun 15 NovAlmere Muziekwijk 13:20Partial coverage0 min—
Sat 14 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Fri 13 NovAlmere Muziekwijk 13:19Partial coverage+1 min—
Thu 12 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Wed 11 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Tue 10 NovAlmere Muziekwijk 13:19Partial coverage+2 min+2 min
Mon 9 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Sun 8 NovAlmere Muziekwijk 13:19Partial coverage+2 min+2 min
Sat 7 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Fri 6 NovAlmere Muziekwijk 13:19No data—
Thu 5 NovAlmere Muziekwijk 13:19No data—
Wed 4 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Tue 3 NovAlmere Muziekwijk 13:19No data—
Mon 2 NovAlmere Muziekwijk 13:19Partial coverage0 min—
Sat 31 OctAlmere Muziekwijk 13:20Partial coverage+1 min—
Fri 30 OctAlmere Muziekwijk 13:19Partial coverage0 min—
Thu 29 OctAlmere Muziekwijk 13:24No data—
Wed 28 OctAlmere Muziekwijk 13:190 min—
Tue 27 OctAlmere Muziekwijk 13:19Partial coverage0 min—
Mon 26 OctAlmere Muziekwijk 13:20No data—
Sun 25 OctAlmere Muziekwijk 13:20No data—
Sat 24 OctAlmere Muziekwijk 13:19Partial coverage0 min—
Fri 23 OctAlmere Muziekwijk 13:20No data—
Thu 22 OctAlmere Muziekwijk 13:20No data—
Wed 21 OctAlmere Muziekwijk 13:22No data—
Tue 20 OctAlmere Muziekwijk 13:19Partial coverage0 min—
Mon 19 OctAlmere Muziekwijk 13:21Partial coverage0 min—
Sun 18 OctHilversum Sportpark 12:56+1 min—
Sat 17 OctHilversum Sportpark 12:57No data—