Train NS 4084 Gouda – Amsterdam Centraal

Gouda 23:49 → Amsterdam Centraal 00:43 Daily 0 h 54 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 00:29

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 00:43 · 2 km/h

  1. Gouda23:49
  2. Woerden00:01
  3. Breukelen00:11
  4. Amsterdam Holendrecht00:23
  5. Duivendrecht00:30
  6. Amsterdam Amstel00:34
  7. Amsterdam Centraal00:43

Today it is running no worse than usual: typical arrival delay is 0 min; 96% of the last 23 runs arrived on time.

On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 2 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 15 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 Amsterdam 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

  • Mon 12 Oct Max en route +11 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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 10Today
23:49on time on time
23:52≈ on time ≈ on time
00:01 / 00:03≈ on time ≈ on time
00:11≈ on time ≈ on time
00:20≈ on time ≈ on time
00:23≈ on time ≈ on time
00:25 / 00:28≈ on time ≈ on time
00:30≈ on time ≈ on time
00:34≈ on time ≈ on time
00:38≈ on time ≈ on time
00:43on 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

DateLast stopFinalMax
Fri 6 Nov— 00:290 min—
Thu 5 Nov— 00:44No data—
Wed 4 Nov— 00:44+1 min—
Mon 2 Nov— 00:430 min—
Sun 1 NovWoerden 00:170 min—
Sat 31 Oct— 00:450 min—
Fri 30 Oct— 01:280 min—
Wed 28 Oct— 00:430 min—
Tue 27 Oct— 00:450 min—
Mon 26 Oct— 00:430 min—
Sun 25 OctAmsterdam Muiderpoort 00:53No data—
Sat 24 Oct— 00:470 min—
Fri 23 Oct— 00:440 min—
Thu 22 Oct— 00:510 min—
Wed 21 Oct— 00:440 min—
Tue 20 Oct— 00:460 min—
Sat 17 OctAmsterdam Muiderpoort 00:510 min—
Fri 16 Oct— 00:590 min—
Thu 15 Oct— 00:430 min—
Wed 14 Oct— 00:440 min—
Tue 13 Oct— 00:500 min—
Mon 12 Oct— 01:02+9 min+11 min
Sun 11 OctWoerden 00:170 min—
Sat 10 Oct— 00:540 min—
Fri 9 Oct— 00:430 min—
Thu 8 Oct— 00:500 min—
Tue 6 Oct— 00:440 min—
Mon 5 OctBreukelen 00:430 min—
Sun 4 OctAmsterdam Muiderpoort 00:53No data—
Sat 3 OctDuivendrecht 00:48No data—