Train NS 3193 Den Haag Centraal – Utrecht Centraal

Den Haag Centraal 00:01 → Utrecht Centraal 01:04 Daily 1 h 03 min · 6 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: tomorrow 00:01 from Den Haag Centraal · Mon 16 Nov

Next departure 00:01 tomorrow · Den Haag Centraal
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 23 full · 1 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 34 full · 1 partial · 7 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 Utrecht Centraal, 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 35 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
00:01on time on time
00:12 / 00:14≈ on time ≈ on time
00:30 / 00:33≈ on time ≈ on time
00:39 / 00:42≈ on time ≈ on time
00:48≈ on time ≈ on time
01:04on 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
Sat 14 Nov— 01:040 min—
Thu 12 Nov— 01:040 min—
Tue 10 Nov— 01:040 min—
Mon 9 Nov— 01:040 min—
Sun 8 NovAmsterdam Bijlmer ArenA 01:040 min—
Sat 7 Nov— 01:030 min—
Fri 6 Nov— 01:040 min—
Thu 5 Nov— 01:040 min—
Wed 4 Nov— 01:220 min—
Mon 2 Nov— 01:040 min—
Sun 1 NovAmsterdam Bijlmer ArenA 01:090 min—
Sat 31 Oct— 01:030 min—
Fri 30 Oct— 01:040 min—
Wed 28 Oct— 01:060 min—
Tue 27 Oct— 01:050 min—
Mon 26 Oct— 01:050 min—
Sun 25 OctAmsterdam Bijlmer ArenA 01:070 min—
Sat 24 Oct— 01:060 min+2 min
Thu 22 Oct— 01:050 min—
Wed 21 Oct— 01:070 min—
Tue 20 Oct— 01:050 min—
Mon 19 Oct— 01:050 min—
Sun 18 OctAmsterdam Bijlmer ArenA 01:060 min—
Sat 17 OctAmsterdam Bijlmer ArenA 01:04Partial coverage0 min—
Fri 16 Oct— 01:040 min—
Thu 15 Oct— 01:050 min—
Wed 14 Oct— 01:070 min—
Tue 13 Oct— 01:060 min—
Mon 12 Oct— 01:050 min—
Sun 11 OctAmsterdam Bijlmer ArenA 01:050 min—