Train NS 1722 Amersfoort Vathorst – Den Haag Centraal

Amersfoort Vathorst 07:57 → Den Haag Centraal 09:08 Daily 1 h 11 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 09:10 0 min

  1. Amersfoort Vathorst07:57
  2. Amersfoort Schothorst08:02
  3. Amersfoort Centraal08:06
  4. Utrecht Centraal08:23
  5. Gouda08:46
  6. Den Haag Centraal09:08

Next service: tomorrow 07:57 from Amersfoort Vathorst · Thu 15 Oct

Full trip card
Next departure 07:57 tomorrow · Amersfoort Vathorst
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 22 full · 2 partial · 6 no data
On-time · 90 days
91%
39/43 runs under 3 min
RT coverage: 41 full · 2 partial · 44 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Den Haag 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

  • Fri 9 Oct Max en route +17 min · last fix heading to Gouda +15 min
  • Thu 17 Sept Max en route +6 min · last fix heading to Utrecht Centraal +5 min
  • Wed 16 Sept Max en route +6 min · last fix heading to Amersfoort Centraal +5 min
  • Tue 8 Sept Max en route +7 min · last fix heading to Amersfoort Centraal +5 min

Distribution · 90 days

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

  • Early 58% · 25
  • On time 33% · 14
  • 3–10 min 7% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 90% T n=10
  • 86% W n=7
  • 80% T n=5
  • 89% F n=9
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

StopSched.
Amersfoort Vathorst
07:57
Amersfoort Schothorst
08:02
Amersfoort Centraal
08:06 / 08:10
Utrecht Centraal
08:23 / 08:28
Gouda
08:46 / 08:47
Den Haag Centraal
09:08

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.

Recent runs

DateLast stopFinalMax
Wed 14 OctGouda 09:10Partial coverage0 min—
Tue 13 OctGouda 09:220 min—
Mon 12 OctGouda 09:20Partial coverage0 min—
Sun 11 OctAmersfoort Centraal 09:16+1 min—
Sat 10 OctAmersfoort Centraal 09:14+1 min—
Fri 9 OctGouda 09:37+15 min+17 min
Thu 8 OctGouda 09:11+1 min—
Wed 7 OctGouda 09:100 min—
Tue 6 OctGouda 09:090 min—
Mon 5 OctGouda 09:04−1 min+1 min
Sun 4 OctAmersfoort Centraal 08:24No data—
Sat 3 OctAmersfoort Centraal 08:24No data—
Fri 2 OctGouda 09:02−10 min—
Thu 1 OctGouda 09:03No data—
Wed 30 SeptUtrecht Centraal 18:39−5 min—
Tue 29 SeptGouda 09:02−2 min—
Mon 28 SeptAmersfoort Centraal 17:26+1 min+4 min
Sun 27 SeptAmersfoort Centraal 08:25No data—
Sat 26 SeptAmersfoort Centraal 08:24No data—
Fri 25 SeptAmersfoort Centraal 22:56−3 min+5 min
Thu 24 SeptAmersfoort Centraal 21:54−3 min+10 min
Wed 23 SeptAmersfoort Centraal 18:51−13 min+3 min
Tue 22 SeptAmersfoort Centraal 17:39−6 min+7 min
Mon 21 SeptAmersfoort Centraal 19:16−7 min—
Sun 20 SeptAmsterdam Zuid 09:00No data—
Sat 19 SeptAmsterdam Zuid 09:000 min+5 min
Fri 18 SeptAmersfoort Centraal 00:46−2 min+2 min
Thu 17 SeptUtrecht Centraal 09:57+5 min+6 min
Wed 16 SeptAmersfoort Centraal 18:32+5 min+6 min
Tue 15 SeptAmersfoort Centraal 17:22−3 min+2 min