Train NS 4920 Utrecht Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 07:25 from Utrecht Centraal · Thu 5 Nov

Next departure 07:25 today · Utrecht Centraal
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 10 full · 11 partial · 7 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 10 full · 12 partial · 62 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: +2 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

  • Sat 17 Oct Max en route +8 min · last fix heading to Hilversum Sportpark +7 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Almere Muziekwijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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