Private Transportation Companies - Summary and Trip Data
Data and Resources
-
trips_and_summary_readmePDF
-
trips_sampleCSV
-
summary_statsCSV
-
summary_stats.csvCSV
-
summary_stats.xmlXML
-
summary_stats.jsonJSON
-
trips_sample.csvCSV
-
trips_sample.xmlXML
-
trips_sample.jsonJSON
-
trips_2018.zipZIP
-
trips_2019.zipZIP
-
trips_2020.zipZIP
-
trips_2021.zipZIP
-
trips_2022.zipZIP
-
trips_2023.zipZIP
-
trips_2024.zipZIP
-
trips_2025.zipZIP
-
trips_2026.zipZIP
Additional Info
| Field | Value |
|---|---|
| Dataset Category | Table |
| Refresh Rate | Monthly |
| Collection Method | Private Transportation Companies submit Trip and Driver Availability Records as a condition of operating in the City of Toronto under [Regulation 546-116](https://www.toronto.ca/legdocs/municode/toronto-code-546.pdf). * Trip records * These records include pickup and drop-off locations, along with timestamps for key points in the journey such as the request time, acceptance time, driver arrival time, pickup time, and drop-off time * Additional information is provided: * For completed trips, records include the fare paid before fees and taxes, as well as the reported distance travelled * For cancelled trips, the driver or passenger must provide a cancellation reason * Driver availability records * These records capture the periods when a vehicle is available to accept customer trips * They include the time and location marking the start and end of a vehicle shift |
| Excerpt | This dataset includes detailed trip data from Private Transportation Companies operating in the City, as well as a daily summary of trip and vehicle operating statistics. |
| Limitations | * Data collected by the City include only passenger trips that start or end in Toronto and portions of vehicle activity occurring within Toronto. Delivery activity, even if conducted on a platform owned by a PTC, is not included. * Fare data reflect the amount paid by the customer before discounts and tips and do not represent driver earnings. * The City combines data from all PTCs and applies a deduplication process to remove overlapping vehicle activity across platforms. This ensures that time and distance are not counted multiple times when drivers are active on multiple apps. * Distance travelled during periods when not engaged with a customer is estimated by routing between the start and end points of each availability period. Routing is based on the fastest travel-time path and may not reflect the actual path taken while drivers are searching for customers. The estimation method does not capture circulating without a destination and may therefore underestimate distance in such cases. * Although the City’s deduplication process accounts for trips fulfilled on multiple platforms, drivers may still be travelling for other reasons (e.g. fulfilling food deliveries which are not reported here, commuting) while available. * Please consult the Technical Documentation for detailed descriptions of the data processes discussed above. The document also includes dates with missing data and any changes made to the datasets since publishing. * Files other than the **summary\_stats** and **trips\_sample** files below exceed one million rows and are not suitable for Excel. We recommend using Python or R for analysis. If using Excel, you may use "Data > Get Data > From File" to safely import data from an external file into a pivot table. |
| Owner Division | Transportation Services |
| Owner Section | Policy, Data & Strategic Initiatives (PDSI) |
| Owner Unit | Transportation Data & Analytics |
| Owner Email | vfhopendata@toronto.ca |
| Author Email | vfhopendata@toronto.ca |
| Maintainer Email | vfhopendata@toronto.ca |
| Author | vfhopendata@toronto.ca |
| Civic Issues | Mobility |
| Formats |
|
| Topics |
|
| Source | |
| Information URL | |
| Image URL | |
| Last Updated | 2026-04-01 20:02:21 |
| Is Retired? | |
| Date Published | 2026-03-04 14:08:37.958534 |