Train NS 3164 Nijmegen – Den Haag Centraal

Nijmegen 17:58 → Den Haag Centraal 19:59 Daily 2 h 01 min · 10 stops NS (Nederlandse Spoorwegen)

Running now · updated 18:24

Heading to Den Haag Centraal 0 min

Estimated arrival at Den Haag Centraal 19:59 · 137 km/h

  1. Nijmegen17:58
  2. Ede-Wageningen18:26
  3. Veenendaal-De Klomp18:32
  4. Amsterdam Bijlmer ArenA19:12
  5. Amsterdam Zuid19:19
  6. Leiden Centraal19:46
  7. Den Haag Centraal19:59

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

On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 18 full · 2 partial · 10 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 21 full · 2 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 5 Oct Max en route +16 min · last fix heading to Nijmegen +16 min
  • Fri 9 Oct Max en route +13 min · last fix heading to Veenendaal-De Klomp +10 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Nijmegen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 4% · 1
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
17:58on time on time
18:10 / 18:16≈ on time ≈ on time
18:26≈ on time ≈ on time
18:32≈ on time ≈ on time
18:51 / 18:56≈ on time ≈ +1 min
19:12 / 19:13≈ on time ≈ +1 min
19:19 / 19:20≈ on time ≈ +1 min
19:27 / 19:29≈ on time ≈ +1 min
19:46 / 19:48≈ on time ≈ +1 min
19:59on time +1 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 NovArnhem Centraal 18:19Partial coverage0 min—
Thu 5 NovNijmegen 20:04No data—
Wed 4 NovNijmegen 19:590 min—
Tue 3 NovNijmegen 19:59No data—
Mon 2 NovNijmegen 20:020 min—
Sun 1 NovLeiden Centraal 20:03+1 min+2 min
Sat 31 OctLeiden Centraal 20:02+1 min+1 min
Fri 30 OctDriebergen-Zeist 20:000 min—
Thu 29 Oct— 20:010 min+1 min
Wed 28 Oct— 20:150 min—
Tue 27 Oct— 19:51No data—
Mon 26 OctLeiden Centraal 20:000 min—
Sun 25 OctLeiden Centraal 20:02No data—
Sat 24 OctLeiden Centraal 20:040 min—
Fri 23 OctAmsterdam Zuid 20:000 min—
Thu 22 OctDriebergen-Zeist 20:170 min—
Wed 21 Oct— 20:01No data—
Tue 20 OctDriebergen-Zeist 20:050 min—
Mon 19 OctEde-Wageningen 20:010 min—
Sun 18 OctLeiden Centraal 20:020 min+1 min
Sat 17 OctLeiden Centraal 20:02No data—
Fri 16 OctLeiden Centraal 20:02No data—
Thu 15 OctEde-Wageningen 20:05No data—
Wed 14 OctLeiden Centraal 20:19No data—
Tue 13 OctEde-Wageningen 20:01No data—
Mon 12 OctEde-Wageningen 18:390 min—
Sun 11 OctLeiden Centraal 20:03+1 min+3 min
Sat 10 OctLeiden Centraal 20:03+1 min—
Fri 9 OctVeenendaal-De Klomp 20:23Partial coverage+10 min+13 min
Thu 8 OctNijmegen 20:11+5 min+5 min