Train NS 4949 Almere Centrum – Utrecht Centraal

Almere Centrum 14:21 → Utrecht Centraal 15:05 Daily 0 h 44 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:21 from Almere Centrum · Fri 6 Nov

Next departure 14:21 today · Almere Centrum
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 5 full · 14 partial · 10 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 5 full · 17 partial · 66 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 Utrecht Centraal, 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 24 Oct Max en route +6 min · last fix heading to Utrecht Overvecht +5 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 95% · 21
  • 3–10 min 5% · 1
  • 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
  • 75% 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
14:21on time on time
14:24≈ on time ≈ on time
14:28≈ on time ≈ on time
14:39 / 14:42≈ on time ≈ on time
14:47 / 14:48≈ on time ≈ +1 min
14:50≈ on time ≈ +1 min
15:01≈ on time ≈ +1 min
15:05on time +1 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
Thu 5 NovUtrecht Overvecht 15:14No data—
Wed 4 NovUtrecht Overvecht 15:14Partial coverage+1 min—
Tue 3 NovUtrecht Overvecht 15:15No data—
Mon 2 NovUtrecht Overvecht 15:14Partial coverage0 min—
Sun 1 NovUtrecht Overvecht 15:160 min—
Sat 31 OctUtrecht Overvecht 15:15Partial coverage0 min—
Fri 30 OctUtrecht Overvecht 15:15No data—
Thu 29 OctUtrecht Overvecht 15:15Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 15:150 min—
Tue 27 OctUtrecht Overvecht 15:15No data—
Mon 26 OctUtrecht Overvecht 15:15No data—
Sun 25 OctUtrecht Overvecht 15:22No data—
Sat 24 OctUtrecht Overvecht 15:19Partial coverage+5 min+6 min
Fri 23 OctUtrecht Overvecht 15:15Partial coverage0 min—
Thu 22 OctUtrecht Overvecht 15:17No data—
Wed 21 OctUtrecht Overvecht 15:20No data—
Tue 20 OctUtrecht Overvecht 15:15Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 15:16Partial coverage0 min—
Sun 18 OctUtrecht Overvecht 15:150 min—
Sat 17 OctUtrecht Overvecht 15:160 min—
Fri 16 OctUtrecht Overvecht 15:18Partial coverage0 min—
Thu 15 OctUtrecht Overvecht 15:15No data—
Wed 14 OctUtrecht Overvecht 15:26Partial coverage0 min—
Tue 13 OctUtrecht Overvecht 15:15No data—
Mon 12 OctUtrecht Overvecht 15:15Partial coverage0 min—
Sun 11 OctUtrecht Overvecht 15:16+2 min+2 min
Sat 10 OctUtrecht Overvecht 15:15Partial coverage0 min—
Fri 9 OctUtrecht Overvecht 15:15Partial coverage0 min—
Thu 8 OctUtrecht Overvecht 15:15Partial coverage0 min—
Wed 7 OctUtrecht Overvecht 15:16Partial coverage+1 min+2 min