Train NS 3134 Nijmegen – Den Haag Centraal

Nijmegen 10:28 → Den Haag Centraal 12:30 Daily 2 h 02 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Nijmegen10:28
  2. Arnhem Centraal10:40
  3. Utrecht Centraal11:17
  4. Amsterdam Bijlmer ArenA11:38
  5. Amsterdam Zuid11:44
  6. Leiden Centraal12:13
  7. Den Haag Centraal12:30

Next service: tomorrow 10:28 from Nijmegen · Fri 13 Nov

Next departure 10:28 tomorrow · Nijmegen
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 19 full · 1 partial · 10 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 62 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: +3 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

  • Sun 1 Nov Max en route +7 min · last fix heading to 's-Hertogenbosch +7 min
  • Sat 31 Oct Max en route +6 min · last fix heading to Leiden Centraal +5 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 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
10:28on time on time
10:40 / 10:45≈ on time ≈ on time
10:55≈ on time ≈ on time
11:17 / 11:21≈ on time ≈ +1 min
11:38≈ on time ≈ +1 min
11:44 / 11:49≈ on time ≈ +1 min
11:55 / 11:56≈ on time ≈ +1 min
12:13 / 12:18≈ on time ≈ +1 min
12:30on time +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:32Partial coverage0 min—
Wed 11 NovLeiden Centraal 12:33+1 min—
Tue 10 NovLeiden Centraal 12:33+1 min+1 min
Mon 9 NovLeiden Centraal 12:32+1 min+1 min
Sun 8 NovLeiden Centraal 12:34+2 min+3 min
Sat 7 NovLeiden Centraal 12:320 min—
Fri 6 NovLeiden Centraal 12:33No data—
Thu 5 NovLeiden Centraal 12:320 min—
Wed 4 NovLeiden Centraal 12:330 min+2 min
Tue 3 NovLeiden Centraal 12:33No data—
Mon 2 NovLeiden Centraal 12:330 min—
Sun 1 Nov's-Hertogenbosch 11:34+7 min+7 min
Sat 31 OctLeiden Centraal 12:42+5 min+6 min
Fri 30 OctLeiden Centraal 12:33No data—
Thu 29 OctLeiden Centraal 12:320 min—
Wed 28 OctLeiden Centraal 12:320 min—
Tue 27 OctLeiden Centraal 12:33No data—
Mon 26 OctLeiden Centraal 12:320 min—
Sun 25 OctLeiden Centraal 12:33No data—
Sat 24 OctAmsterdam Zuid 12:330 min—
Fri 23 OctLeiden Centraal 12:330 min—
Thu 22 OctLeiden Centraal 12:330 min—
Wed 21 OctLeiden Centraal 12:33No data—
Tue 20 OctLeiden Centraal 12:320 min—
Mon 19 OctLeiden Centraal 12:340 min—
Sun 18 OctLeiden Centraal 12:320 min—
Sat 17 OctLeiden Centraal 12:32No data—
Fri 16 OctLeiden Centraal 12:34No data—
Thu 15 OctLeiden Centraal 12:32No data—
Wed 14 OctLeiden Centraal 12:32No data—