Much attention regarding transit priority in recent months focused on the RapidTO red lanes for 29/929 Dufferin and 510 Bathurst, and on traffic signal timings for 6 Finch West, 5 Eglinton and a few intersections on 510 Spadina. Another change with less fanfare was the modification of parking and stopping restrictions on Dundas Street West between Dovercourt and University.
Council approved these changes in two groups. The first was for the area between Spadina and McCaul, and the second extended this east to University and west to Dovercourt.
In a previous articles, I reviewed the effect of changes on 7 Bathurst between Bathurst Station and Eglinton, and on 511 Bathurst and 29 Dufferin south from Bloor.
This article continues the series with a review of changes on Dundas Street West.
A few noteworthy points:
Over the 29 month period of this review there has been little change in travel times, although there are some specific seasonal and weather-related spikes and dips.
Peak period, peak direction shows more variation than off-peak, especially westbound in the PM peak.
Extended travel times do not occur only in the “downtown” part of the route, nor only in the peak periods. Attempts at transit priority that focus only on the core and the peak periods will not address issues at other times and locations.
There are quite striking “heartbeat” patterns in the data where the highest values usually fall on the same day of the week:
AM peak eastbound: The spikes tend to be on Tuesday or Wednesday. This corresponds to a known pattern that developed during the pandemic that midweek traffic was higher than the ends of the week.
Early and late evening eastbound: The spikes tend to fall late in the week on Thursdays and Fridays. A similar pattern shows up in the late evening westbound.
Although travel times are fairly consistent, they only measure the service that actually shows up. At the end of the article are charts showing headways (the interval between streetcars) both ways at Dufferin, Bathurst and University in May 2026. Travel times might be consistent and even slightly improved, but the overall service quality remains uneven.
As I began to write this on June 6 at 5:00pm, the TTC had not yet published the detailed memo of service changes for June 7. There is a web page listing World Cup related service changes, but no details about service frequencies. On an interim basis, I have used the electronic version of the June 7 schedules (GTFS data) as a source for info on scheduled service. On game days, there will be additional service as needed.
Updated: The TTC issued the detailed service memo in the early hours of June 7. Thanks to those burning the midnight oil to get this out. This article has been updated to consolidate info from the memo. Note that June service changes for subway, LRT and bus routes will not occur until June 21, and these will be covered in a separate post.
307 and 311 Bathurst night services: Stopping arrangements at Bathurst and St. Clair West Stations clarified.
Streetcar route maps added at the end of the article.
301L route clarified to include extension to Dufferin Loop.
Streetcar vehicle allocation tables added.
Spreadsheet of detailed changes added. Revised to include 929 Dufferin Express.
List of destination sign changes added.
Bathurst Corridor
Night service on 307 Bathurst bus will be shortened to end at Bathurst Station. Service south to Exhibition will be provided by a 311 Bathurst night car running from St. Clair to Exhibition Loop.
Service on 511 Bathurst will be improved (see table later in this article).
Updates:
307 buses will loop through Bathurst Station, but will lay over and serve a new stop northbound on Bathurst at London (opposite the station).
311 streetcars will run out of service through St. Clair West Station.
Spadina Corridor
Service on the 510 Spadina streetcar will be shortened to turn at Queens Quay Loop. Service to Union Station will be provided by 509/309 Harbourfront and by 310 Spadina. (Corrected)
Waterfront
Service on 509 Harbourfront will be improved (see table later in this article), and a new 309 Harbourfront night car will operate.
Dufferin Corridor
Service on 929 Dufferin express will be added on Sunday evenings on Game Days running every 8 minutes.
King Corridor
Service will be improved on 504 King. On Game Days, the 504B from Broadview Station will turn back via a loop of King, Queen and Shaw without serving Dufferin Loop. See detailed map and schedule in the schedule section later in this article.
Queen / Lake Shore Boulevard West
507/501/301 Long Branch service will be replaced by buses due to construction at Long Branch Loop.
Two branches of the replacement bus service will operate:
507 from Humber Loop to Long Branch Loop via Park Lawn.
507M from Humber Loop to the Humber Bay Shores area looping via Marine Parade Drive.
This configuration will run until Labour Day weekend. In September, 507 streetcars will return as far as Kipling Loop, and the 110 Islington South will be extended west to Long Branch Loop.
508 Lake Shore streetcar service will be suspended for the summer season returning after Labour Day.
Updated: 301L night buses will operate from Long Branch Loop to Dufferin Loop via Queen and Dufferin providing an overlap with the 301 Queen night car.
See map in the schedule details later in this post.
This article updates previously published on the Dufferin bus and Bathurst streetcar routes to show how the travel times in affected areas changed with the gradual implementation of red lanes over past months.
In summary, there is a reduction in travel time during some periods, but not others, typically because congestion is not an issue all of the time. An important factor, one we saw some years back on King Street, is not just to lower travel times, but to reduce the variations that contribute to irregular headways.
With a reserved lane, periods that might not be badly congested all the time have extra protection against surges like special events or construction projects that remove some network capacity. This depends on enforcement, of course, and paint alone will not keep motorists out of transit lanes.
The balance of the article shows how travel times have evolved from 2024 to May 2026 as a reference point before the World Cup events stress the transit and road system.
Also shown here are the headways on the three services from terminals and along the route. This is a very serious problem, and, indeed, the Achilles’ Heel of the RapidTO scheme. It is not enough to reduce travel times by a few minutes if the service reliability is poor.
Riders are more sensitive to wait times than travel times, especially over shorter distances because the unreliability of a wait contributes substantially to total travel time. On a route like Dufferin with local and express service, the short travel time can be completely outweighed by the longer wait for a bus which is also likely to be crowded when it eventually arrives.
With the opening of Line 5 Eglinton on February 8, the former 35 Jane bus was split in two. This article reviews the headway reliability on the new services, with a look back at November 2025 as a comparison. Service in the Jane corridor was notoriously erratic. It has been proposed as a RapidTO red lane route, but nothing has actually been implemented yet.
The original service operated from Jane Station to Pioneer Village Station. At the north end, the service divides with half of the buses running via Jane to Steeles, and half via Hullmar. This arrangement is preserved in the new 35 Jane whose southern terminus is Mount Dennis Station. (Map on the left below)
The new 27 Jane South route runs from Mount Dennis Station to Jane Station. (Map on the right)
There was no change in the 935 Jane Express which continues to run directly between Jane and Pioneer Village Stations.
By comparison with the service in Fall 2025, operations on the 27/35 route pair are an improvement, but this starts from a very low bar. Headways along the route are scattered over a wide range of values making service for riders quite unpredictable. There is no change in service behaviour over the three month period indicating that there was no effort to improve performance, or there was, it had no effect.
With the many route changes for the opening of Lines 5 and 6, an obvious “project” is to review how all of the new and updated routes are operating. I cannot guarantee that I will get to them all, but will nibble away at the list.
We still cannot see vehicle tracking data for 5 Eglinton LRT, but a route we can see is the vestigial replacement bus 34 Eglinton.
Full disclosure: The Eglinton East corridor is one I have used all of my life, and quality of service affects me personally. However, it also affects the many would-be riders along the line for whom transit “service” has all but disappeared.
This route shows a classic laissez-faire attitude of TTC management where buses appear to run more or less on a schedule of their own making. Riders on other routes are familiar with this problem, but 34 Eglinton shows how an infrequent service can be left to rot and discourage riders from using it. TTC has even talked of the 20-minute service as “interim” and that it might be cut in the future.
The idea of a parallel surface bus was to provide accessibility for those who could not walk to an LRT station, and this is, in theory, a key part of accessibility for the line. However, service is so erratic on this nominally 20-minute route that actually catching a bus requires good timing through a transit app to find one. To add insult to injury, the TTC removed several stops along Eglinton just before Line 5 opened, adding access time to the remaining riders in the name of speeding up a frequent bus service that was about to vanish.
TTC talks about its “family of services” scheme that encourages potential Wheel-Trans users to make part of their trip on the conventional system. 34 Eglinton demonstrates just how badly they actually deliver alternatives.
There is no excuse for the poor quality of service on this route, and three months’ data show that the current operation is “normal” with no visible effort to rein in irregularities.
This article updates a series of posts looking at the 7 Bathurst bus and the effect of transit priority changes made on that route. Originally the City and TTC had proposed red lanes from Bathurst Station north to Eglinton. This was substantially changed to parking and turning restrictions, and the elimination of some transit stops. The changes predominantly affected northbound travel and in the interest of brevity, I have included mainly northbound data here. The changes implemented were:
Extendind the no stopping period on the east side of Bathurst between Eglinton and Bathurst Station North Exit from 2:00 to 7:00pm, weekdays, and from noon to 7:00pm, weekends, except public holidays. Previously, there was no stopping from 4:00 to 6:00pm or 3:30 to 7:00pm, Monday to Friday, depending on the segment
No left turns northbound from 7:00am to 7:00pm Monday to Saturday, except public holidays (Toronto Transit Commission vehicles excepted), at Bathurst & Davenport northbound, and at Bathurst & Dupont southbound. Previous hours were 4:00 to 6:00pm weekdays northbound at Davenport, and 7am to 6pm southbound at Dupont.
The existing no left turns restriction northbound at Bathurst & Dupont from 7:00 to 9:00am weekdays was removed.
Concurrently with these changes, the TTC removed stops from the route, mostly north of St. Clair, with the premise that fewer stops would make faster trips. The actual effect varies depending on how heavily a stop is used, whether each bus or only some trips actually stop there, and whether there is an associated traffic signal that could compound the delay of serving a stop.
A saving of 1/3 in travel times has been claimed between Bathurst Station and Dupont, but this is not supported by actual tracking data. There may be best case comparisons where there is a 1/3 saving, but this does not apply across the board. The primary intent, as explained in the presentation to Council at the time, was to improve the reliability of travel times, not to speed up service.
A major issue on Bathurst is that the service is infrequent (generally every 10 minutes) and very unreliable. How much road capacity should be dedicated to such a route by comparison with other priority implementations such as on King Street or Eglinton Avenue East?
The first set of charts in this article shows the evolution of travel times between Barton (just north of Bathurst Station), St. Clair and Eglinton. The second compares April 2026 with April 2025 in detail. The third reviews the history of headway reliability on the route.
Effective April 27, streetcar service on 501 Queen resumed its normal route between Broadview and Parliament rather than diverting via Dundas Street.
The 503 Kingston Road bus also resumed its normal route between the Don River and Parliament running via King rather than via Queen.
The split operation of 504 King with all streetcars running to Distillery Loop and a 504D shuttle between Parliament and Broadview Station will continue until the schedule change on May 3 when full streetcar service over 504 will resume. Similarly the split 304 King night car and 301 Queen night bus operation will be replaced with 304 streetcars over the full route.
This change has been announced by the TTC via a press release, but does not appear on their Service Changes page. The underlying online schedules will not be updated until May 3, and so trip prediction apps will not give valid information for 501 and 503 services between Broadview and Parliament in the interim.
For a complete list of current and past streetcar diversions, see my Where Is My Streetcar page.
TTC Plans for service to the six World Cup games to be played in Toronto, as well as to the nearby Fan Fest area, were covered in a presentation deck in a recent TTC Board agenda. Because the Board had been rather chatty on previous items, this one was not presented although there was a media scrum afterward.
The plan for transportation to the venues depends on a combination of routes. However, the description of the service varies between the presentation deck and info on the TTC’s World Cup web page.
On the left, the presentation clearly shows the 63 Ossington bus as a World Cup route, but it is missing on the web page.
According to the web page, there will be “expanded service” on subway lines 1 and 2, and “enhanced sevice” on 29/929 Dufferin. Service on 504 King, 509 Harbourfront and 511 Bathurst will run every 5 minutes all day on game days.
Because the 509 and 511 streetcars merge at Bathurst and Fleet, this will mean a 2’30” combined service to Exhibition Loop. That is substantial by current TTC streetcar standards, but it will only provide 24 cars per hour with a capacity of 3,600 riders, generously allowing for 150 per car. The stress on service will be stronger after games when many fans want to leave in a short period. Whether the combined streetcar, bus and GO train service will be able to handle this remains to be seen.
Note the planned access routes to the queuing area on Fleet Street includes fare payment points. This will allow the loading to occur from a fare paid zone without the delay of on board taps, and without the need for fare enforcement in a congested area. This is also shown for access to a contingency bus area at Fort York and Lake Shore, and it is reasonable to assume the same approach will be used at Dufferin Loop.
Aggressive transit priority measures will be needed to keep streets clear. Toronto does not have a good history in restricting motorists to leave the streets for transit service, and the affected areas are not just the downtown business district but residential streets.
Both Bathurst and Dufferin Streets will, by the time of the matches, have RapidTO red lanes south from Bloor. Early plans for Bathurst called for express streetcars and local bus service, but that scheme has been dropped.
I asked Josh Colle, TTC’s Chief Strategy and Customer Experience Officer, about this, and here is his reply:
Earlier iterations of our conceptual service plan envisioned removing intermediate stops along 511 Bathurst to increase the speed of travel along the corridor during the World Cup. Bus service would be provided to serve all existing stops.
With the expected travel time improvements from RapidTO, the implementation of 6-minute or better service, and further service increases during the World Cup period, the express streetcar concept was abandoned. There were also concerns about buses operating in the dedicated lanes and needing to merge in and out of potentially congested curb lanes to serve curbside stops.
This was originally seen as an opportunity to pilot a stop removal program for streetcar while operating a local bus service. However, given the recent priority to improving streetcar operations through other initiatives, our focus remains providing the best service for all customers during the World Cup period.
The TTC intends to provide Blue Night service as shown on the map below beyond the usual level.
Things do go wrong, inevitably, and here are the TTC’s preparations:
Service delivery and performance:
Supplementary supervisors in stations, on-street, and at key locations
Additional standby and change-off vehicles on all modes
Enhanced station staff, customer service and ambassadors
Real-time system oversight and coordinated decision making
Infrastructure readiness:
Streetcar switch duty operators at critical points
Extra janitorial and vehicle cleaning crews
Additional line mechanics, elevator, overhead, subway, signal, and track crews
Standby streetcar support and service trucks
Emergency safety:
Added security personnel on match days
Toronto Police paid duty officers EMS at key locations
Coordinated approach with Station staff, Transit Control and Special Constables
Continued access to social supports and resources through partnerships
This is substantially more than we see for day-to-day operations, and there may be some lessons to be learned about the level of supervisory and support services needed to handle major events and their demand.
(The reference to switch duty operators is a tad embarrassing considering that the planned streetcar routes do not involve any manual switches, and this does not show great confidence in their existing technology.)
There will be “testing exercises” although the exact scale of these is not yet known.
Finally there are plans for enhanced and visible safety and security with the use of Special Constables, Fare Inspectors (Provincial Offenses Officers) and contract security staff. Ideally, as many riders as possible will pass through fare controls at some point in their journey and extensive fare checks on board will not be needed. More important will be visibility of staff who can intervene, if only to report issues and act as a visible deterrent.
Management will bring an updated plan to the June 3 Board meeting.
In response to the “Toronto has the world’s slowest streetcars” meme floating around on line and among some transit advocates, various proposals were floated to speed up our system.
One of these is the idea that there are too many streetcar stops, and if only cars didn’t pause so often for passengers, we could have faster streetcar service. The TTC’s euphemism for this is “stop balancing”.
A chart accompanying the TTC report shows the speed and stop spacing values for several transit systems. Toronto is down in the left bottom corner with the closes stops and the slowest speed. However, Melbourne’s trams are in the same range as Toronto for stop spacing, but they operate faster. Nowhere does the TTC examine what differences might apply to Melbourne lines, nor for the other systems that are both faster and with wider stop spacing.
Although there are some outliers, the bulk of the data points are in the 400-500m range, but this does not examine route characteristics. The original study of slow Melbourne streetcars by Dr. Jan Scheurer commented about Toronto that “CBD-typical speeds seem to extend across the entire city” [p. 8]. Riders who sit in traffic jams on King or Queen Street West, or on Queen Street in the Beach are quite familiar with this problem. Toronto streetcars do not emerge from the core to fly into nearby suburbs.
There is also the issue that Toronto streetcars used to move faster both with the CLRV fleet and the PCCs that preceded them. Something beyond stop spacing is at work even on routes with dedicates rights-of-way. It is easy to go after stops as a source of delay because this would not require an examination of TTC operating practices and the City’s lack of aggressive transit signal priority. Indeed, during the last round of major works on St. Clair, it was discovered that TSP was not actually working in many locations.
Source: TTC
For the sake of argument, assume that the delays to TTC streetcars come from closely spaced stops. Any rider knows that there are other factors including slow operation through junctions, traffic signals that do not give streetcars priority and congestion both in the core and the outer parts of many routes.
The premise is that fewer stops will speed service benefiting those already on streetcars at the expense of those who have to walk further to a stop. This is a bogus argument regardless of stop spacing. There will almost always be more riders passing any individual stop who would “benefit” from its elimination than riders who use the stop. The same argument could be made for some subway stations.
Here are the TTC’s Board-approved stop spacing standards. The target range of 300-400m for local surface routes implies an average stop spacing of 350m giving some leeway to adjust to conditions.
(To give readers a sense of distance, a subway station platform is about 150m long, and so a 300m walk is from one end of a station platform to the other and return.)
Streetcar route averages lie roughly in the 250m-325m range below the standard’s midpoint of 350m. Some stop trimming has already occurred to eliminate very closely spaced stops.
Note that 508 Lake Shore shows the same average as 507 Long Branch even though the 508 travels into the core. The reason is that the stop spacing between Humber Loop and Roncesvalles is quite wide, and this offsets the closer spacing on King Street in the average.
Route
Termini
Stop Spacing (m)
501 Queen
Neville-Roncesvalles (*)
241
Roncesvalles-Humber
448
503 Kingston Road
Victoria Park-York
284
504 King
Dundas West Stn-Distillery (*)
283
Dufferin Loop-Broadview Stn (*)
280
505 Dundas
Dundas West Stn-Broadview Stn (*)
278
506 Carlton
High Park-Main Station (*)
260
507 Long Branch
Long Branch Loop-Humber Loop
312
508 Lake Shore
Long Branch Loop-Distillery
306
509 Harbourfront
Exhibition-Union Station
373
510 Spadina
Spadina Station-Queens Quay
293
511 Bathurst
Bathurst Station-Exhibition Loop
328
512 St. Clair
Gunns Loop-St. Clair Station
270
Source: Calculated from TTC GTFS Schedule Data
Notes:
501 Queen stop data are taken from the pre-Ontario Line construction with service running directly across Queen from Church to York.
Stops near Dundas West and Broadview Stations that are used primarily by overnight services have not been included in the stop counts for 504 King and 505 Dundas.
506 Carlton stop data are taken from the through route before construction diversion around Bay & College.
Some Basic Math
If one wants to achieve a major saving from stop time, many stops have to be cut on a route. One or two will annoy their regular users, but the change in travel time, if any, will be quite small and disappear into the background noise of other variations.
The basic calculation is simple: if a route now has an average spacing of 300m, and you want to raise this to 400m, then one quarter of the stops must vanish. The bigger the change in stop spacing, the more stops must be eliminated.
The numbers of stops for various spacings per 1km are shown below:
250m: 4.0
300m: 3.3
350m: 2.9
400m: 2.5
450m: 2.2
500m: 2.0
With the TTC standard of 300-400m, 350m falls half way along, or 2.9 stops/km. Just to bring routes now at a 250m spacing (4.0/km) to that level would require a reduction of about 1.1 stop/km, or about 12 stops each way on a route the length of 505 Dundas (11km).
If the goal is to move to a 400-500m standard, this means the new target average would be 450m. A route whose average is now 250m would lose almost half its stops. This would be extremely difficult as routes do not have that many “unimportant” closely-space stops to begin with.
The effect would not be on a few riders at a few minor stops, but on many riders all along the routes. They would face extra walking distance lengthening overall travel times, not to mention accessibility issues for those with mobility challenges.
A simple, but important, number is not the space between adjacent stops, but the space that would result if any stop were removed. (In other words, the space between stop N and stop N±2.) In some cases, the existing TTC standard would still be met, but in many the gap between stops would be well outside the standard. For example, if three stops are each 300m apart, getting rid of the middle one creates a 600m gap, well above the standard.
Stops cannot simply be re-spaced to maintain uniformity or iron out problems with stop elimination. For pedestrian safety, stops are almost always at signaled intersections or at least at pedestrian crosswalks so that riders can cross safely to/from stops on the opposite side of the street. The existing street layout, signal patterns and major destinations such as transfer points determine where stops might go. Toronto, unlike Manhattan, does not have a repeating grid as a base for designing standards.
In the sections that follow, I will turn to a few sample routes. There are occasional closely-spaced stops, some with good reason, but not many are ripe for plucking without adopting a considerable increase in the standard and substantial cut to the number of stops. This should be a conscious policy debate, not a change buried in a wider review of Service Standards without a clear indication of the effects on routes across the city.
This post continues a series of articles reviewing travel times for streetcar and bus operations on 510 Spadina. Recent events include winter storms, temporary bus substitution for one week in February 2026 due to power supply issues, and implementation of better transit priority at three intersections.
This article includes data from January 2024 through March 2026 showing travel times on Spadina. Also included are comparisons of speeds and dwell times along the route from October 2025 and March 2026.
For an extended period in 2024-25, the 510 route operated with buses and was, for a time, diverted to St. George Station. Comparisons between streetcar and bus travel times varied through this period depending on the location, time of day, traffic conditions and the degree of priority given to buses, if any.
In February 2026, signals at College, Queen Dundas and King were modified to give streetcars a clear signal before allowing left turns. In the data to March 31, the effect of this change is small. At the level of an individual intersection, this is hard to measure because the change in wait time for a signal is comparable to the frequency with which streetcars report their location. This problem is discussed in more detail at the end of the article. [Corrected at 5:45pm, April 6]
Although signals may clear for streetcars more quickly, there is no change in TTC operating practices that force vehicles to crawl through intersections. The results were not as good as I had hoped, and there are areas on 510 Spadina that need priority far more than the three intersections modified so far.
At this point, confirmation of the benefit of signal changes awaits more data as well as possible expansion of the program.
More generally, the three modified intersections are only part of a larger route, and not necessarily the primary source of delay. Any attempt to improve 510 Spadina travel times must look at the whole route, and at the many locations where streetcars can be delayed.
One point of interest is that streetcar travel times rose slightly after the period of bus operation compared to before (Spring 2025 vs Spring 2024). The change is small but noticeable. What made the difference?
The City and TTC must address why it is possible for buses in mixed traffic to outrun streetcars on reserved lanes during periods when traffic is not congested. A mixture of signalling, stop location and TTC operating practices make this possible.
My apologies to readers who say “oh no, not more charts” and move on to something else. I have deliberately included a lot of them here so that those who are interested can see how the data behave. Any suggestions for changes in presentation or analysis are welcome.
Steve Munro 