Why six Toronto map records cannot describe a mobile-reader fleet.
The October 3, 2026 FlockDetour snapshot contains six mapped ALPR records within 16.1 km of central Toronto and none attributed to Flock Safety, but Toronto Police describes Axon readers installed in patrol vehicles, which a fixed-location snapshot cannot count.
Six mapped records, four directions, no verification dates
The snapshot was retrieved at 13:54 UTC on October 3 around 43.6532, −79.3832, using the same 16.1-km (10-mile) radius as the US reports. Six records passed the ALPR and distance filters. None were attributed to Flock Safety; four included a recorded direction and none included a last-verification date.
The selected entries cluster around 43.64, −79.38, south of the reference point. Three have an Axis vendor label, one is labeled Avigilon and two have no vendor recorded. Axis and Axon are different names; a source entry labeled Axis must not be relabeled Axon because a police program uses Axon.
All six are database records, not an independently inspected inventory. The lack of Flock attribution in this small mapped sample is not evidence that no Flock devices exist in Toronto. It is also not evidence that Toronto has only six licence-plate readers.
Toronto coverage page and all six selected records · Inspect an Axis-labeled record · Inspect the Avigilon-labeled record
Toronto Police describes a moving system
The Toronto Police Service technology page, accessed October 3, identifies Axon as its ALPR provider and says more than 560 vehicles are equipped. The page describes alerts in patrol vehicles. This is the service's account of its program, not a fleet audit performed for this report.
A mobile reader travels with a vehicle. A fixed point on a community map cannot describe everywhere that vehicle may be or infer where it will scan next. Subtracting six map entries from a police vehicle count would create a misleading coverage percentage because the sources count different units.
For the police program, consult the service's own technology page and its supporting oversight materials. For a specific fixed installation, inspect the map record and original source. Do not transfer one vendor's data-retention policy, ownership or operating rules onto every Toronto map point.
How we counted—and what the date means
FlockDetour retrieved public camera records on October 3, 2026, selected the ALPR camera class, excluded records marked removed, and measured a 10-mile (16.1-km) circle from the stated reference point. Overlapping query results were deduplicated by record ID. Larger query boxes were split when the server result limit was reached; these three reported city snapshots had no unresolved result cap.
A record ID identifies a database entry, not necessarily a distinct pole or physical device. Nearby entries can describe different viewing directions, separate devices or duplicates. Flock attribution follows the source vendor label; other and unidentified vendors stay separate. The results do not establish who owns each device, whether it is operating or whether a particular vehicle would be captured.
The retrieval date is when we read the database. It is not an installation date, a field visit or a last-seen date. None of the records in these three snapshots supplied a last-verification date. Source corrections and removals can change a later count without a new installation or physical removal occurring that day.
Camera sources and attribution · Why camera-map counts disagree
Use ALPR as the category and verify the vendor separately
Searching for “Flock cameras in Toronto” can lead to information about automatic licence plate recognition generally. Flock Safety is one vendor; it is not a synonym for every ALPR or ANPR installation. This report keeps the query useful by showing what the map actually labels and linking the distinct police program.
A useful correction includes the location, evidence for the device type and vendor, and when it was observed. Missing or sparse mapping should guide further research, not a camera-free claim. This article is published by FlockDetour, the map and app maker, and does not report a driving test or independently endorse a route.
ALPR cameras in Canada: vendors and map limits · Browse US and Canadian city coverage
Questions people ask
Does zero Flock attribution mean Toronto has no Flock cameras?
Are Toronto Police vehicle readers included as six fixed points?
Are Axis and Axon the same vendor?
Related guides
Flock cameras in Canada: check ALPR records and the vendor · Why do Flock camera maps show different counts? · DeFlock, FlockHopper and FlockDetour compared · All guides · Live camera map · Get the app
Sources
- October 3 Toronto snapshot: six ALPR records, no Flock attribution, within 16.1 km; later page refreshes may differ from this fixed report
- Toronto Police Service: ALPR technology: official account naming Axon and describing readers in more than 560 vehicles, accessed October 3, 2026
- FlockDetour camera sources: source attribution and import context; map data is community reported and incomplete
FlockDetour is independent and is not affiliated with or endorsed by Flock Safety or any surveillance vendor.