Train NS 1789 Utrecht Centraal – Deventer

Utrecht Centraal 00:07 → Deventer 00:57 Daily 0 h 50 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 3 November 0 min

Next service: tomorrow 00:07 from Utrecht Centraal · Fri 6 Nov

Next departure 00:07 tomorrow · Utrecht Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 3 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 12 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 Deventer, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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:07on time on time
00:20 / 00:22≈ on time ≈ on time
00:46 / 00:47≈ on time ≈ on time
00:57on 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
Tue 3 Nov— 00:580 min—
Sun 1 NovUtrecht Centraal 00:190 min—
Fri 30 Oct— 00:340 min—
Tue 27 Oct— 00:580 min—
Sun 25 OctUtrecht Centraal 00:280 min—
Sat 24 Oct— 02:15No data—
Fri 23 Oct— 01:50+2 min+4 min
Thu 22 Oct— 01:130 min—
Wed 21 Oct— 01:030 min—
Tue 20 Oct— 00:59+1 min+2 min
Sun 18 OctUtrecht Centraal 00:210 min—
Sat 17 OctUtrecht Centraal 00:200 min—
Thu 15 Oct— 00:20No data—
Wed 14 Oct— 00:20No data—
Tue 13 Oct— 00:200 min—
Sun 11 OctUtrecht Centraal 00:210 min—
Thu 8 Oct— 00:580 min—
Sun 4 OctUtrecht Centraal 00:21No data—
Sat 3 OctAmersfoort Centraal 00:36No data—
Sun 27 SeptUtrecht Centraal 00:21No data—
Sun 6 SeptUtrecht Centraal 00:21No data—
Sun 30 AugUtrecht Centraal 00:21No data—
Sun 23 AugUtrecht Centraal 00:21No data—
Sat 22 AugWoerden 00:03No data—
Sun 16 AugUtrecht Centraal 00:21No data—
Sun 9 AugUtrecht Centraal 00:21No data—