83 7098 Canadian Border – Toronto

View line 83

Canadian Border 17:45 → Toronto 19:43 Daily 1 h 58 min · 6 stops US

It has not run yet today

Last recorded run: Friday 2 October 0 min

Next service: today 17:45 from Canadian Border · Mon 16 Nov

Next departure 17:45 today · Canadian Border
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 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 Toronto, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 37 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
17:45on time on time
18:08≈ on time ≈ on time
18:27≈ on time ≈ on time
19:04≈ on time ≈ on time
19:19≈ on time ≈ on time
19:43on 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 10 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 2 Oct— 17:110 min—
Thu 1 Oct— 19:580 min—
Wed 30 Sept— 19:590 min—
Tue 29 Sept— 19:590 min—
Mon 28 Sept— 19:590 min—
Sun 27 Sept— 19:590 min—
Sat 26 Sept— 19:590 min—
Thu 24 Sept— 23:490 min—
Wed 23 Sept— 19:590 min—
Tue 22 Sept— 18:590 min—
Sun 20 Sept— 19:540 min—
Sat 19 Sept— 19:580 min—
Thu 17 Sept— 00:580 min—
Wed 16 Sept— 19:590 min—
Tue 15 Sept— 19:590 min—
Mon 14 Sept— 19:590 min—
Sun 13 Sept— 19:590 min—
Fri 11 Sept— 19:460 min—
Thu 10 Sept— 19:580 min—
Wed 9 Sept— 19:580 min—
Tue 8 Sept— 19:580 min—
Mon 7 Sept— 19:590 min—
Sun 6 Sept— 19:590 min—
Sat 5 Sept— 19:590 min—
Fri 4 Sept— 16:000 min—
Thu 3 Sept— 19:590 min—
Tue 1 Sept— 00:350 min—
Mon 31 Aug— 19:590 min—
Sun 30 Aug— 19:590 min—
Sat 29 Aug— 19:590 min—