Train NS 3147 Den Haag Centraal – Nijmegen

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

Running now · updated 14:02

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 14:32

  1. Den Haag Centraal12:31
  2. Leiden Centraal12:42
  3. Amsterdam Zuid13:12
  4. Amsterdam Bijlmer ArenA13:20
  5. Utrecht Centraal13:38
  6. Arnhem Centraal14:15
  7. Nijmegen14:32

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

On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
98%
61/62 runs under 3 min
RT coverage: 51 full · 11 partial · 27 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: 0 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 11 Oct Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 31% · 19
  • On time 68% · 42
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=10
  • 100% W n=9
  • 100% T n=8
  • 100% F n=9
  • 100% S n=8
  • 83% S n=6

Stops and timetable

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

Last 90 days, 62 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:31on time on time
12:42 / 12:47≈ on time ≈ on time
13:03 / 13:05≈ on time ≈ on time
13:12 / 13:15≈ on time ≈ +1 min
13:20 / 13:22≈ on time ≈ +1 min
13:38 / 13:43≈ on time ≈ +1 min
14:05≈ on time ≈ +1 min
14:15 / 14:20≈ on time ≈ +1 min
14:32on 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
Wed 11 NovArnhem Centraal 13:59Partial coverage0 min—
Tue 10 NovArnhem Centraal 14:34Partial coverage0 min—
Mon 9 NovArnhem Centraal 14:34Partial coverage0 min—
Sun 8 NovArnhem Centraal 14:35+1 min+2 min
Sat 7 NovArnhem Centraal 14:340 min—
Fri 6 NovArnhem Centraal 14:34No data—
Thu 5 NovArnhem Centraal 14:34Partial coverage0 min—
Wed 4 NovArnhem Centraal 14:34Partial coverage0 min—
Tue 3 NovArnhem Centraal 14:34Partial coverage0 min—
Mon 2 NovArnhem Centraal 14:34Partial coverage0 min—
Sun 1 NovSittard 15:41+2 min+4 min
Sat 31 OctVeenendaal-De Klomp 14:140 min—
Fri 30 OctVeenendaal-De Klomp 14:16No data—
Thu 29 OctVeenendaal-De Klomp 14:210 min—
Wed 28 OctVeenendaal-De Klomp 14:21No data—
Tue 27 OctVeenendaal-De Klomp 14:20No data—
Mon 26 OctVeenendaal-De Klomp 14:210 min—
Sun 25 OctVeenendaal-De Klomp 14:15No data—
Sat 24 OctVeenendaal-De Klomp 14:140 min—
Fri 23 OctUtrecht Centraal 13:540 min—
Thu 22 OctUtrecht Centraal 13:54No data—
Wed 21 OctUtrecht Centraal 13:54No data—
Tue 20 OctUtrecht Centraal 13:54No data—
Mon 19 OctArnhem Centraal 14:34Partial coverage0 min—
Sun 18 OctArnhem Centraal 14:340 min—
Sat 17 OctArnhem Centraal 14:340 min—
Fri 16 OctArnhem Centraal 14:34No data—
Thu 15 OctArnhem Centraal 14:34No data—
Wed 14 OctArnhem Centraal 14:35No data—
Tue 13 OctArnhem Centraal 14:34No data—