The TTC has now added 6 Finch to the collection of published delay data available on the City of Toronto’s Open Data site. See:
The data are in a summary format, much less detailed than the version on which I based a recent article, but they have the advantage of being in spreadsheet format that makes general analysis easier.
In the form published by the TTC, the data include:
- Date and time of the event
- Location
- Event Code
- Minutes of delay and gap
- Direction
- Vehicle number
- List of event codes
For the purpose of this article, I sorted and summarized the events by code and by the number of times it was reported. (If you want to see the full unedited list, download the file from the City’s site.)
What is immediately obvious here is that the majority of the delays are due to equipment and infrastructure failures, and that a few individual events caused extended outages. These are numbers as reported by the TTC, and do not really show the degree to which 6 Finch was effectively unavailable to riders who had to use shuttle buses instead.
Overall, in the period from December 7-31 there were 350 events.
Updated January 21, 2026 at 10:40pm:
By comparison, the streetcar network, with many longer routes in a more challenging operating environment, had only 819 events between them. Of these, 22 were infrastructure issues (with only 2 switch issues), 74 were due to equipment issues and 113 to diversions. Common incidents were due, broadly speaking, to passenger issues: 102 ill patrons, 106 unsanitary cars, and 169 security issues (most commonly “disorderly patron”).
| 501 Queen | 160 | 509 Harbourfront | 23 |
| 504 King | 166 | 510 Spadina | 75 |
| 505 Dundas | 124 | 511 Bathurst | 59 |
| 506 Carlton | 115 | 512 St. Clair | 69 |
| 507 Long Branch | 28 |
Steve Munro 