Train NS 4984 Utrecht Centraal → Almere Oostvaarders

Utrecht Centraal 23:11 → Almere Oostvaarders 00:06 Daily 0 h 55 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 23:11 from Utrecht Centraal · Sat 21 Nov

Next departure 23:11 today · Utrecht Centraal
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 5 no data
On-time · 90 days
94%
34/36 runs under 3 min
RT coverage: 36 full · 0 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Almere Oostvaarders, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 19 Nov Max en route +10 min · last fix heading to — +8 min
  • Fri 16 Oct Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=5
  • 67% T n=3
  • 83% F n=6
  • 100% S n=3
  • 100% S n=6

Stops and timetable

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

Last 90 days, 36 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:11on time on time
23:15≈ on time ≈ on time
23:23≈ on time ≈ +1 min
23:27≈ on time ≈ +1 min
23:30 / 23:32≈ on time ≈ +1 min
23:38≈ on time ≈ +1 min
23:48≈ on time ≈ +2 min
23:52≈ on time ≈ +2 min
23:55 / 23:56≈ on time ≈ +2 min
23:59≈ on time ≈ +2 min
00:02≈ on time ≈ +2 min
00:06on time +3 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
Fri 20 Nov— 00:120 min+1 min
Thu 19 Nov— 00:24+8 min+10 min
Wed 18 Nov— 00:090 min—
Tue 17 Nov— 00:09+1 min+2 min
Mon 16 NovUtrecht Centraal 00:090 min—
Sun 15 NovAlmere Muziekwijk 00:190 min+1 min
Sat 14 Nov— 00:090 min—
Fri 13 Nov— 00:090 min—
Thu 12 Nov— 00:09+1 min—
Wed 11 Nov— 00:090 min+2 min
Tue 10 Nov— 00:090 min—
Mon 9 Nov— 00:090 min+2 min
Sun 8 NovAlmere Muziekwijk 00:190 min—
Sat 7 Nov— 00:090 min—
Fri 6 Nov— 00:12+2 min+2 min
Thu 5 Nov— 00:14No data—
Wed 4 Nov— 00:090 min—
Tue 3 Nov— 00:090 min—
Sun 1 NovAlmere Muziekwijk 00:190 min+1 min
Sat 31 Oct— 00:09No data—
Fri 30 Oct— 00:09No data—
Wed 28 Oct— 00:09No data—
Tue 27 Oct— 00:070 min—
Mon 26 Oct— 00:100 min—
Sun 25 OctAlmere Muziekwijk 00:190 min—
Sat 24 Oct— 00:12No data—
Fri 23 Oct— 00:10+2 min+2 min
Thu 22 Oct— 00:09No data—
Wed 21 Oct— 00:10No data—
Tue 20 Oct— 00:100 min—