Train NS 4973 Almere Centrum – Utrecht Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

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

Next departure 20:21 today · Almere Centrum
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 7 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 29 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: +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

  • Wed 4 Nov Max en route +10 min · last fix heading to — +10 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
20:21on time on time
20:24≈ on time ≈ on time
20:28≈ on time ≈ +1 min
20:39 / 20:42≈ on time ≈ +1 min
20:47 / 20:48≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
21:01≈ on time ≈ +2 min
21:05on 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
Thu 5 Nov— 21:040 min—
Wed 4 Nov— 21:24+10 min+10 min
Mon 2 Nov— 21:040 min—
Sun 1 NovUtrecht Overvecht 21:14+1 min+1 min
Sat 31 OctUtrecht Overvecht 21:150 min—
Fri 30 Oct— 21:07No data—
Thu 29 Oct— 21:060 min—
Wed 28 Oct— 21:090 min—
Tue 27 Oct— 21:13No data—
Mon 26 Oct— 21:090 min—
Sun 25 OctUtrecht Overvecht 21:16No data—
Sat 24 OctUtrecht Overvecht 21:20No data—
Fri 23 Oct— 21:08+1 min+1 min
Thu 22 Oct— 21:070 min—
Wed 21 Oct— 21:070 min—
Tue 20 Oct— 21:130 min—
Mon 19 Oct— 21:130 min—
Sun 18 OctUtrecht Overvecht 21:150 min—
Sat 17 OctUtrecht Overvecht 21:150 min—
Fri 16 Oct— 21:12+5 min+5 min
Thu 15 Oct— 21:06No data—
Wed 14 Oct— 21:07No data—
Tue 13 Oct— 23:22No data—
Mon 12 Oct— 21:090 min—
Sun 11 OctUtrecht Overvecht 21:150 min—
Sat 10 OctUtrecht Overvecht 21:15+1 min—
Fri 9 Oct— 21:10+1 min+2 min
Thu 8 Oct— 21:05+1 min+2 min
Wed 7 Oct— 21:11+2 min+2 min
Tue 6 Oct— 21:07+1 min+3 min