Train NS 4982 Utrecht Centraal – Almere Centrum

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 22:54 from Utrecht Centraal · Fri 6 Nov

Full trip card
Next departure 22:54 today · Utrecht Centraal
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 14 full · 3 partial · 10 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 17 full · 3 partial · 24 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: +3 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 2 Nov Max en route +11 min · last fix heading to — +11 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 12 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 10% · 2
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 100% T n=3
  • 100% W n=3
  • 0% T n=1
  • 100% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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
Utrecht Centraal
22:54on time on time
Utrecht Overvecht
22:58≈ on time ≈ on time
Hollandsche Rading
23:05≈ on time ≈ +1 min
Hilversum Sportpark
23:09≈ on time ≈ +1 min
Hilversum
23:11 / 23:12≈ on time ≈ +1 min
Naarden-Bussum
23:17 / 23:20≈ on time ≈ +2 min
Almere Poort
23:31≈ on time ≈ +3 min
Almere Muziekwijk
23:35≈ on time ≈ +3 min
Almere Centrum
23:38on 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
Thu 5 Nov— 23:54No data—
Wed 4 Nov— 23:390 min—
Mon 2 Nov— 23:54+11 min+11 min
Sun 1 NovAlmere Muziekwijk 23:49Partial coverage0 min—
Sat 31 OctNaarden-Bussum 23:48Partial coverage0 min—
Fri 30 Oct— 23:39No data—
Wed 28 Oct— 23:39No data—
Tue 27 Oct— 23:40No data—
Mon 26 Oct— 23:390 min—
Sun 25 OctAlmere Muziekwijk 23:49No data—
Sat 24 Oct— 00:02No data—
Fri 23 Oct— 23:400 min—
Thu 22 Oct— 23:39No data—
Wed 21 Oct— 23:39No data—
Tue 20 Oct— 23:390 min—
Mon 19 Oct— 23:390 min—
Sun 18 OctHilversum Sportpark 23:240 min—
Sat 17 OctHilversum Sportpark 23:25No data—
Fri 16 Oct— 23:390 min—
Thu 15 Oct— 23:39No data—
Wed 14 Oct— 23:390 min—
Tue 13 Oct— 23:390 min—
Mon 12 Oct— 23:46+3 min+3 min
Sun 11 OctAlmere Muziekwijk 23:53Partial coverage+3 min+7 min
Sat 10 Oct— 23:400 min—
Fri 9 Oct— 23:400 min—
Thu 8 Oct— 23:46+4 min+4 min
Wed 7 Oct— 23:400 min+1 min
Tue 6 Oct— 23:390 min—
Mon 5 Oct— 23:40+1 min+2 min