Train NS 4944 Utrecht Centraal – Almere Centrum

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

✓ Today’s run finished

Today, last fix heading to Almere Muziekwijk at 14:19 0 min

  1. Utrecht Centraal13:25
  2. Utrecht Overvecht13:29
  3. Hilversum Sportpark13:39
  4. Naarden-Bussum13:47
  5. Almere Poort14:01
  6. Almere Muziekwijk14:05
  7. Almere Centrum14:08

Next service: tomorrow 13:25 from Utrecht Centraal · Sun 8 Nov

Next departure 13:25 tomorrow · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 4 full · 14 partial · 12 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 4 full · 18 partial · 67 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: 0 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

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

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

On-time by weekday

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

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
13:25on time on time
13:29— —
13:39— —
13:41 / 13:42— —
13:47 / 13:50— —
14:01— —
14:05— —
14: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
Sat 7 NovAlmere Muziekwijk 14:19Partial coverage0 min—
Fri 6 NovAlmere Muziekwijk 14:19No data—
Thu 5 NovAlmere Muziekwijk 14:23No data—
Wed 4 NovAlmere Muziekwijk 14:19Partial coverage0 min—
Tue 3 NovAlmere Muziekwijk 14:19No data—
Mon 2 NovAlmere Muziekwijk 14:19Partial coverage0 min—
Sun 1 NovAlmere Muziekwijk 14:210 min—
Sat 31 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Fri 30 OctAlmere Muziekwijk 14:19No data—
Thu 29 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Wed 28 OctAlmere Muziekwijk 14:210 min—
Tue 27 OctAlmere Muziekwijk 14:19No data—
Mon 26 OctAlmere Muziekwijk 14:21No data—
Sun 25 OctAlmere Muziekwijk 14:22No data—
Sat 24 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Fri 23 OctAlmere Muziekwijk 14:27Partial coverage0 min—
Thu 22 OctAlmere Muziekwijk 14:19No data—
Wed 21 OctAlmere Muziekwijk 14:31No data—
Tue 20 OctAlmere Muziekwijk 14:20Partial coverage0 min—
Mon 19 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Sun 18 OctHilversum Sportpark 13:560 min—
Sat 17 OctHilversum Sportpark 13:54No data—
Fri 16 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Thu 15 OctAlmere Muziekwijk 14:19No data—
Wed 14 OctAlmere Muziekwijk 14:20Partial coverage0 min—
Tue 13 OctAlmere Muziekwijk 14:19No data—
Mon 12 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Sun 11 OctAlmere Muziekwijk 14:190 min—
Sat 10 OctAlmere Muziekwijk 14:19Partial coverage0 min—
Fri 9 OctAlmere Muziekwijk 14:19Partial coverage0 min—