Train NS 3140 Nijmegen – Den Haag Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:58 from Nijmegen · Thu 5 Nov

Next departure 11:58 today · Nijmegen
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 13 full · 4 partial · 12 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 69 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

  • Sat 10 Oct Max en route +30 min · last fix heading to Amsterdam Zuid +30 min
  • Sun 1 Nov Max en route +4 min · last fix heading to 's-Hertogenbosch +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

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

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