Train NS 3145 Den Haag Centraal – Nijmegen

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

Running now · updated 13:18

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 14:02 · 140 km/h

  1. Den Haag Centraal12:01
  2. Leiden Centraal12:12
  3. Amsterdam Zuid12:42
  4. Amsterdam Bijlmer ArenA12:50
  5. Utrecht Centraal13:08
  6. Arnhem Centraal13:45
  7. Nijmegen14:02

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

On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 12 full · 5 partial · 13 no data
On-time · 90 days
99%
66/67 runs under 3 min
RT coverage: 59 full · 8 partial · 22 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: +1 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

  • Thu 10 Sept Max en route +3 min · last fix heading to Den Haag Centraal +3 min

Distribution · 90 days

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

  • Early 28% · 19
  • On time 70% · 47
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 100% W n=8
  • 89% T n=9
  • 100% F n=9
  • 100% S n=11
  • 100% S n=9

Stops and timetable

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

Last 90 days, 67 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
12:01on time on time
12:12 / 12:17≈ on time ≈ on time
12:33 / 12:35≈ on time ≈ +1 min
12:42 / 12:45≈ on time ≈ +1 min
12:50 / 12:52≈ on time ≈ +1 min
13:08 / 13:13≈ on time ≈ +1 min
13:35≈ on time ≈ +2 min
13:45 / 13:50≈ on time ≈ +2 min
14:02on 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
Tue 10 NovUtrecht Centraal 13:14Partial coverage0 min—
Mon 9 NovArnhem Centraal 14:04Partial coverage0 min—
Sun 8 NovArnhem Centraal 14:040 min—
Sat 7 NovArnhem Centraal 14:040 min—
Fri 6 NovArnhem Centraal 14:04No data—
Thu 5 NovArnhem Centraal 14:09No data—
Wed 4 NovArnhem Centraal 14:04Partial coverage0 min—
Tue 3 NovArnhem Centraal 14:09No data—
Mon 2 NovArnhem Centraal 14:08No data—
Sun 1 NovUtrecht Centraal 15:09+3 min+4 min
Sat 31 OctDriebergen-Zeist 13:31+2 min+3 min
Fri 30 OctVeenendaal-De Klomp 13:460 min—
Thu 29 OctVeenendaal-De Klomp 13:500 min—
Wed 28 OctVeenendaal-De Klomp 13:49No data—
Tue 27 OctVeenendaal-De Klomp 13:500 min—
Mon 26 OctVeenendaal-De Klomp 13:490 min—
Sun 25 OctVeenendaal-De Klomp 13:43No data—
Sat 24 OctVeenendaal-De Klomp 13:430 min—
Fri 23 OctUtrecht Centraal 13:230 min—
Thu 22 OctUtrecht Centraal 13:24No data—
Wed 21 OctUtrecht Centraal 13:24No data—
Tue 20 OctUtrecht Centraal 13:240 min—
Mon 19 OctArnhem Centraal 14:07Partial coverage0 min—
Sun 18 OctArnhem Centraal 14:050 min—
Sat 17 OctArnhem Centraal 14:04No data—
Fri 16 OctArnhem Centraal 14:04No data—
Thu 15 OctArnhem Centraal 14:08No data—
Wed 14 OctArnhem Centraal 14:08Partial coverage0 min—
Tue 13 OctArnhem Centraal 14:04No data—
Mon 12 OctArnhem Centraal 14:04No data—