Train NS 3136 Nijmegen → Den Haag Centraal

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

Running now · updated 11:20

Heading to Den Haag Centraal 0 min

Estimated arrival at Den Haag Centraal 12:59 · 162 km/h

  1. Nijmegen10:58
  2. Ede-Wageningen11:26
  3. Veenendaal-De Klomp11:32
  4. Amsterdam Bijlmer ArenA12:12
  5. Amsterdam Zuid12:19
  6. Leiden Centraal12:46
  7. Den Haag Centraal12:59

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

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 8 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 33 full · 3 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=7
  • 100% F n=4
  • 100% S n=7
  • 100% S n=4

Stops and timetable

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

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