Train NS 4938 Utrecht Centraal – Almere Centrum

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

✓ Today’s run finished

Today, last fix heading to Almere Muziekwijk at 12:49 No data

  1. Utrecht Centraal11:55
  2. Utrecht Overvecht11:59
  3. Hilversum Sportpark12:09
  4. Naarden-Bussum12:17
  5. Almere Poort12:31
  6. Almere Muziekwijk12:35
  7. Almere Centrum12:38

Next service: tomorrow 11:55 from Utrecht Centraal · Fri 6 Nov

Next departure 11:55 tomorrow · Utrecht Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 2 full · 16 partial · 11 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 2 full · 18 partial · 68 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

Worst days

  • Sun 11 Oct Max en route +3 min · last fix heading to Almere Muziekwijk +3 min

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 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=2
  • 100% F n=1
  • 100% S n=4
  • 50% 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
11:55on time on time
11:59— —
12:09— —
12:11 / 12:12— —
12:17 / 12:20— —
12:31— —
12:35— —
12:38— —

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