Train NS 4986 Utrecht Centraal – Almere Centrum

Utrecht Centraal 23:54 → Almere Centrum 00:38 Daily 0 h 44 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +4 min

Next service: today 23:54 from Utrecht Centraal · Tue 17 Nov

Next departure 23:54 today · Utrecht Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 17 full · 3 partial · 5 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 27 full · 6 partial · 14 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

  • Mon 16 Nov Max en route +4 min · last fix heading to — +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 83% W n=6
  • 100% T n=2
  • 100% F n=5
  • 100% S n=4
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 stops).

Last 90 days, 33 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
23:54on time on time
23:58≈ on time ≈ on time
00:05≈ on time ≈ +1 min
00:09≈ on time ≈ +1 min
00:11 / 00:12≈ on time ≈ +1 min
00:17 / 00:20≈ on time ≈ +1 min
00:31≈ on time ≈ +2 min
00:35≈ on time ≈ +2 min
00:38on time +2 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
Mon 16 Nov— 00:44+4 min+4 min
Sun 15 NovAlmere Muziekwijk 00:49Partial coverage+2 min+4 min
Sat 14 Nov— 00:390 min—
Fri 13 Nov— 00:390 min—
Thu 12 Nov— 00:390 min—
Wed 11 Nov— 00:390 min—
Tue 10 Nov— 00:390 min—
Mon 9 Nov— 00:390 min—
Sun 8 NovAlmere Muziekwijk 00:49Partial coverage0 min—
Sat 7 Nov— 00:39+1 min+1 min
Fri 6 Nov— 00:390 min—
Thu 5 Nov— 00:39No data—
Wed 4 Nov— 00:49+4 min+4 min
Tue 3 Nov— 00:390 min+2 min
Sun 1 NovAlmere Muziekwijk 00:49Partial coverage+1 min+1 min
Sat 31 Oct— 00:38No data—
Wed 28 Oct— 00:470 min—
Tue 27 Oct— 04:420 min—
Mon 26 Oct— 00:390 min—
Sun 25 OctAlmere Muziekwijk 00:49No data—
Sat 24 Oct— 00:42No data—
Fri 23 Oct— 00:40+2 min+3 min
Thu 22 Oct— 00:40No data—
Wed 21 Oct— 00:430 min—
Mon 19 Oct— 00:42+2 min+4 min
Sun 18 OctAlmere Muziekwijk 00:53Partial coverage0 min—
Sat 17 OctHilversum Sportpark 00:240 min—
Fri 16 Oct— 00:390 min—
Thu 15 Oct— 00:40No data—
Wed 14 Oct— 00:400 min—