Train NS 3141 Den Haag Centraal – Nijmegen

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

✓ Today’s run finished

Today, last fix heading to Arnhem Centraal at 13:04 No data

  1. Den Haag Centraal11:01
  2. Leiden Centraal11:12
  3. Amsterdam Zuid11:42
  4. Amsterdam Bijlmer ArenA11:50
  5. Utrecht Centraal12:08
  6. Arnhem Centraal12:45
  7. Nijmegen13:02

Next service: tomorrow 11:01 from Den Haag Centraal · Sat 7 Nov

Next departure 11:01 tomorrow · Den Haag Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 14 full · 5 partial · 11 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 15 full · 7 partial · 67 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 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

  • Sun 1 Nov Max en route +8 min · last fix heading to Sittard +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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