Train NS 4990 Utrecht Centraal – Almere Centrum

Utrecht Centraal 00:54 → Almere Centrum 01:36 Fri, Sat 0 h 42 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:39 0 min

Utrecht Centraal00:54
Utrecht Overvecht00:58
Hilversum Sportpark01:09
Hilversum01:11
Naarden-Bussum01:17
Almere Muziekwijk01:33
Almere Centrum01:36

Next service: Friday 00:54 from Utrecht Centraal · Fri 13 Nov

Full trip card

Next departure 00:54 Friday · Utrecht Centraal

On-time · 30 days

100%

8/8 runs under 3 min

RT coverage: 8 full · 0 partial · 1 no data

On-time · 90 days

100%

8/8 runs under 3 min

RT coverage: 8 full · 0 partial · 1 no data

Typical delay

0min

Median at arrival, 90 days

30 days: 0 min

P90

0min

9 in 10 runs arrive with less than this

30 days: 0 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

Distribution · 90 days

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

Early 0% · 0
On time 100% · 8
3–10 min 0% · 0
10–30 min 0% · 0
30+ min 0% · 0

On-time by weekday

— M n=0
— T n=0
— W n=0
— T n=0
— F n=0
100% S n=5
100% S n=3

Stops and timetable

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

Last 90 days, 8 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.

Stop	Sched.	Usually	9 days in 10
Utrecht Centraal	00:54	on time	on time
Utrecht Overvecht	00:58	≈ on time	≈ on time
Hollandsche Rading	01:05	≈ on time	≈ on time
Hilversum Sportpark	01:09	≈ on time	≈ on time
Hilversum	01:11 / 01:12	≈ on time	≈ on time
Naarden-Bussum	01:17 / 01:20	≈ on time	≈ on time
Almere Poort	01:29	≈ on time	≈ on time
Almere Muziekwijk	01:33	≈ on time	≈ on time
Almere Centrum	01:36	on time	on time

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

Date	Last stop	Final	Max
Sat 7 Nov	— 01:39	0 min	—
Sun 1 Nov	— 01:39	0 min	—
Sat 31 Oct	— 01:39	0 min	—
Sun 25 Oct	— 01:46	0 min	—
Sat 24 Oct	— 01:40	0 min	—
Sun 18 Oct	Almere Poort 01:45	No data	—
Sat 17 Oct	— 01:39	0 min	—
Sun 11 Oct	— 01:40	0 min	—
Sat 10 Oct	— 01:39	0 min	—