P20 891703 Dijon – Is-sur-Tille

View line P20

Dijon 14:23 → Is-sur-Tille 14:55 0 h 32 min · 7 stops SNCF

Not running right now

Last recorded run: Friday 23 October 0 min

On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Is-sur-Tille, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +5 min · last fix heading to Is-sur-Tille +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
14:23on time on time
14:30 / 14:31≈ on time ≈ on time
14:35 / 14:36≈ on time ≈ on time
14:39 / 14:40≈ on time ≈ on time
14:42 / 14:43≈ on time ≈ on time
14:49 / 14:50≈ on time ≈ on time
14:55on 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
Fri 23 OctIs-sur-Tille 14:560 min—
Thu 22 OctIs-sur-Tille 14:560 min—
Wed 21 OctIs-sur-Tille 14:560 min—
Tue 20 OctIs-sur-Tille 14:560 min—
Mon 19 OctIs-sur-Tille 14:570 min—
Fri 16 OctIs-sur-Tille 14:560 min—
Thu 15 OctIs-sur-Tille 14:560 min—
Wed 14 OctIs-sur-Tille 14:570 min—
Tue 13 OctIs-sur-Tille 14:560 min—
Mon 12 OctIs-sur-Tille 14:560 min—
Fri 9 OctIs-sur-Tille 14:560 min—
Thu 8 OctIs-sur-Tille 15:01+5 min+5 min
Wed 7 OctIs-sur-Tille 14:560 min—
Tue 6 OctIs-sur-Tille 14:560 min—
Mon 5 OctIs-sur-Tille 14:560 min—
Thu 10 SeptStopPoint:OCETrain TER-8771385 14:540 min—
Wed 2 SeptStopPoint:OCETrain TER-8771385 14:550 min—
Tue 1 SeptStopPoint:OCETrain TER-8771385 14:540 min—
Tue 25 AugStopPoint:OCETrain TER-8771385 14:550 min—