Train NS 3132 Nijmegen – Den Haag Centraal

Nijmegen 09:58 → Den Haag Centraal 11:59 Daily 2 h 01 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Leiden Centraal at 12:03 0 min

  1. Nijmegen09:58
  2. Arnhem Centraal10:10
  3. Utrecht Centraal10:47
  4. Amsterdam Bijlmer ArenA11:08
  5. Amsterdam Zuid11:14
  6. Leiden Centraal11:45
  7. Den Haag Centraal11:59

Next service: tomorrow 09:58 from Nijmegen · Fri 13 Nov

Next departure 09:58 tomorrow · Nijmegen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 12 full · 6 partial · 12 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 15 full · 9 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Wed 4 Nov Max en route +4 min · last fix heading to Leiden Centraal +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 67% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 24 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
09:58on time on time
10:10 / 10:15≈ on time ≈ on time
10:25≈ on time ≈ on time
10:47 / 10:51≈ on time ≈ +1 min
11:08≈ on time ≈ +1 min
11:14 / 11:20≈ on time ≈ +1 min
11:27 / 11:29≈ on time ≈ +1 min
11:45 / 11:48≈ on time ≈ +2 min
11:59+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
Thu 12 NovLeiden Centraal 12:03Partial coverage0 min+2 min
Wed 11 NovLeiden Centraal 12:02+1 min+1 min
Tue 10 NovLeiden Centraal 12:03Partial coverage+1 min+3 min
Mon 9 NovLeiden Centraal 12:02Partial coverage0 min—
Sun 8 NovLeiden Centraal 12:03+1 min—
Sat 7 NovLeiden Centraal 12:03+2 min+2 min
Fri 6 NovLeiden Centraal 12:04No data—
Thu 5 NovLeiden Centraal 12:02No data—
Wed 4 NovLeiden Centraal 12:02Partial coverage+4 min+4 min
Tue 3 NovLeiden Centraal 12:03No data—
Mon 2 NovLeiden Centraal 12:03Partial coverage0 min—
Sun 1 Nov's-Hertogenbosch 10:54+1 min+2 min
Sat 31 OctLeiden Centraal 12:030 min—
Fri 30 OctLeiden Centraal 12:020 min—
Thu 29 OctLeiden Centraal 12:050 min—
Wed 28 OctLeiden Centraal 12:02No data—
Tue 27 OctLeiden Centraal 12:020 min—
Mon 26 OctLeiden Centraal 12:020 min—
Sun 25 OctLeiden Centraal 12:04No data—
Sat 24 OctLeiden Centraal 12:03+2 min+2 min
Fri 23 OctLeiden Centraal 12:030 min—
Thu 22 OctLeiden Centraal 12:03No data—
Wed 21 OctLeiden Centraal 12:02No data—
Tue 20 OctLeiden Centraal 12:04No data—
Mon 19 OctLeiden Centraal 12:13Partial coverage0 min—
Sun 18 OctLeiden Centraal 12:03+1 min—
Sat 17 OctLeiden Centraal 12:02No data—
Fri 16 OctLeiden Centraal 12:02No data—
Thu 15 OctLeiden Centraal 12:02No data—
Wed 14 OctLeiden Centraal 12:04No data—