Train NS 5612 Amersfoort Vathorst – Utrecht Centraal

Amersfoort Vathorst 05:39 → Utrecht Centraal 06:09 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 7 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 05:39 from Amersfoort Vathorst · Mon 9 Nov

Next departure 05:39 tomorrow · Amersfoort Vathorst
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 17 full · 1 partial · 2 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 21 full · 1 partial · 41 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 5 Nov Max en route +4 min · last fix heading to Utrecht Overvecht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
05:39on time on time
05:42≈ on time ≈ on time
05:46 / 05:50≈ on time ≈ on time
05:57≈ on time ≈ +1 min
06:00≈ on time ≈ +1 min
06:04 / 06:05≈ +1 min ≈ +2 min
06:09+1 min +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
Fri 6 NovUtrecht Overvecht 06:19No data—
Thu 5 NovUtrecht Overvecht 06:23Partial coverage+4 min+4 min
Wed 4 NovUtrecht Overvecht 06:19+2 min+2 min
Tue 3 NovUtrecht Overvecht 06:190 min—
Mon 2 NovUtrecht Overvecht 06:19No data—
Fri 30 OctUtrecht Overvecht 06:21+2 min+2 min
Thu 29 OctUtrecht Overvecht 06:21+2 min+2 min
Wed 28 OctUtrecht Overvecht 06:200 min—
Tue 27 OctUtrecht Overvecht 06:210 min—
Mon 26 OctUtrecht Overvecht 06:21+1 min+1 min
Fri 23 OctUtrecht Overvecht 06:20+1 min—
Thu 22 OctUtrecht Overvecht 06:200 min—
Wed 21 OctUtrecht Overvecht 06:190 min—
Tue 20 OctUtrecht Overvecht 06:20+1 min+1 min
Mon 19 OctUtrecht Overvecht 06:200 min—
Fri 16 OctUtrecht Overvecht 06:200 min—
Thu 15 OctUtrecht Overvecht 06:200 min+1 min
Wed 14 OctUtrecht Overvecht 06:21+2 min+2 min
Tue 13 OctUtrecht Overvecht 06:22+3 min+3 min
Mon 12 OctUtrecht Overvecht 06:200 min—
Fri 9 OctUtrecht Overvecht 06:20+1 min+1 min
Thu 8 OctUtrecht Overvecht 06:20+2 min+2 min
Wed 7 OctUtrecht Overvecht 06:200 min—
Tue 6 OctUtrecht Overvecht 06:21+2 min+2 min
Mon 5 OctUtrecht Overvecht 06:21No data—
Fri 2 OctUtrecht Overvecht 06:20No data—
Thu 1 OctUtrecht Overvecht 06:20No data—
Wed 30 SeptUtrecht Overvecht 06:19No data—
Tue 29 SeptUtrecht Overvecht 06:20No data—
Mon 28 SeptUtrecht Overvecht 06:20No data—