Train NS Int 9370 Amsterdam Centraal – Paris-Nord

Amsterdam Centraal 16:10 → Paris-Nord 19:45 Mon, Tue, Wed, Thu, Fri, Sun 3 h 35 min · 6 stops NS Int

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:10 from Amsterdam Centraal · Thu 5 Nov

Next departure 16:10 today · Amsterdam Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 10 full · 4 partial · 11 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 12 full · 4 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Paris-Nord, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=3
  • 100% T n=1
  • 100% F n=4
  • — S n=0
  • 100% S n=3

Stops and timetable

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

Last 90 days, 16 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
16:10on time on time
16:24 / 16:27≈ on time ≈ on time
16:53 / 16:58≈ on time ≈ on time
17:30 / 17:33≈ on time ≈ on time
18:06 / 18:13≈ on time ≈ on time
19:45on time on time

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 NovRotterdam Centraal 17:12Partial coverage0 min—
Tue 3 NovRotterdam Centraal 17:12No data—
Mon 2 NovRotterdam Centraal 17:12Partial coverage0 min—
Sun 1 NovRotterdam Centraal 17:120 min—
Fri 30 OctRotterdam Centraal 17:120 min—
Thu 29 OctRotterdam Centraal 17:12No data—
Wed 28 OctRotterdam Centraal 17:12Partial coverage0 min—
Tue 27 OctRotterdam Centraal 17:12No data—
Mon 26 OctRotterdam Centraal 17:12No data—
Sun 25 OctRotterdam Centraal 17:12No data—
Fri 23 OctRotterdam Centraal 17:160 min—
Thu 22 OctRotterdam Centraal 17:12No data—
Wed 21 OctRotterdam Centraal 17:16No data—
Tue 20 OctRotterdam Centraal 17:29No data—
Mon 19 OctRotterdam Centraal 17:160 min—
Sun 18 OctRotterdam Centraal 17:120 min—
Fri 16 OctRotterdam Centraal 17:130 min—
Thu 15 OctRotterdam Centraal 17:17No data—
Wed 14 OctRotterdam Centraal 17:12No data—
Tue 13 OctRotterdam Centraal 17:12No data—
Mon 12 OctRotterdam Centraal 17:14Partial coverage0 min—
Sun 11 OctRotterdam Centraal 17:120 min—
Fri 9 OctRotterdam Centraal 17:130 min—
Thu 8 OctRotterdam Centraal 17:120 min—
Wed 7 OctRotterdam Centraal 17:120 min—
Tue 6 OctRotterdam Centraal 17:120 min—
Mon 5 OctRotterdam Centraal 17:120 min—
Fri 2 OctRotterdam Centraal 17:13No data—
Thu 1 OctRotterdam Centraal 17:12No data—
Wed 30 SeptRotterdam Centraal 17:12No data—