Train NS 3173 Den Haag Centraal – Nijmegen

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

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 19:01 from Den Haag Centraal · Thu 12 Nov

Next departure 19:01 today · Den Haag Centraal
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 25 full · 2 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Nijmegen, 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 +20 min · last fix heading to — +19 min
  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Arnhem Centraal +4 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 11% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
19:01on time on time
19:12 / 19:14≈ on time ≈ on time
19:30 / 19:33≈ on time ≈ +1 min
19:39 / 19:41≈ on time ≈ +1 min
19:46 / 19:47≈ on time ≈ +1 min
20:03 / 20:09≈ on time ≈ +2 min
20:27≈ on time ≈ +3 min
20:33≈ on time ≈ +3 min
20:44 / 20:50≈ on time ≈ +3 min
21:02on time +4 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
Wed 11 Nov— 21:030 min—
Tue 10 Nov— 21:04+1 min+1 min
Mon 9 Nov— 21:030 min—
Sun 8 NovArnhem Centraal 21:04+2 min+2 min
Sat 7 NovArnhem Centraal 21:040 min—
Fri 6 Nov— 21:04+1 min+1 min
Thu 5 Nov— 21:04No data—
Wed 4 Nov— 21:04+5 min+5 min
Tue 3 Nov— 21:03No data—
Mon 2 Nov— 21:04No data—
Sun 1 NovSittard 22:040 min—
Sat 31 OctVeenendaal-De Klomp 20:460 min—
Fri 30 Oct— 20:370 min—
Thu 29 Oct— 20:36+4 min+4 min
Wed 28 Oct— 19:130 min—
Tue 27 Oct— 20:38No data—
Mon 26 OctAmsterdam Bijlmer ArenA 20:38No data—
Sun 25 OctVeenendaal-De Klomp 20:44No data—
Sat 24 OctVeenendaal-De Klomp 20:440 min—
Fri 23 OctLeiden Centraal 20:180 min—
Thu 22 Oct— 20:19No data—
Wed 21 Oct— 20:19No data—
Tue 20 Oct— 20:180 min—
Mon 19 Oct— 21:040 min—
Sun 18 OctArnhem Centraal 21:08+4 min+4 min
Sat 17 OctArnhem Centraal 21:040 min—
Fri 16 OctAmsterdam Bijlmer ArenA 21:03Partial coverage+1 min+1 min
Thu 15 Oct— 21:10No data—
Wed 14 OctAmsterdam Bijlmer ArenA 21:03No data—
Tue 13 Oct— 21:04No data—