46,754 count points
600,551 annual average daily-flow observations covering 2000 to 2025.
Context, not a company score. These observations describe roads, casualties, traffic count points and transport-access infrastructure. They do not measure a company's safety record, operating quality or exposure. The 2025 collision data are provisional.
Collision records149,399
Traffic observations600,551
Traffic count points46,754
NaPTAN access nodes362,520
Recorded road collisions by year
Fatal, serious and slight columns count published casualty-severity aggregates attached to the collision records. They are not interchangeable with collision counts.
| Year | Collision records | Vehicles reported | Fatal casualties | Serious casualties | Status |
|---|---|---|---|---|---|
| 2025 | 48,472 | 87,805 | 735 | 13,171 | Provisional |
| 2024 | 100,927 | 183,514 | 1,602 | 26,040 | Final |
Local-authority review queue
Authorities are ordered by published fatal-plus-serious casualty counts across the available 2024–2025 records. Population, road mileage and traffic exposure are not normalised, so this is a review queue rather than a rate comparison.
| Local authority | Collision records | Fatal casualties | Serious casualties |
|---|---|---|---|
| Birmingham | 3,413 | 37 | 687 |
| Leeds | 2,177 | 20 | 673 |
| E06000065 | 1,535 | 41 | 422 |
| Bradford | 1,477 | 16 | 432 |
| Manchester | 1,068 | 11 | 390 |
| Sheffield | 1,172 | 12 | 388 |
| Glasgow City | 919 | 9 | 360 |
| Westminster | 1,632 | 6 | 349 |
| Wiltshire | 1,364 | 24 | 323 |
| Cornwall | 1,372 | 28 | 312 |
| Southwark | 1,314 | 5 | 326 |
| Doncaster | 762 | 25 | 287 |
| Liverpool | 1,279 | 6 | 304 |
| County Durham | 674 | 32 | 273 |
| Wakefield | 861 | 23 | 281 |
| Lambeth | 1,313 | 6 | 275 |
| Dorset | 988 | 17 | 264 |
| E06000066 | 1,182 | 35 | 244 |
| Kirklees | 916 | 7 | 272 |
| East Riding of Yorkshire | 886 | 21 | 258 |
Infrastructure coverage
362,520 access nodes
Published access points for stops, stations and other public-transport infrastructure. Counts describe the imported register, not service frequency or accessibility quality.
| Publisher node-type code | Access nodes |
|---|---|
BCT | 345,884 |
BCS | 4,139 |
RSE | 3,866 |
RLY | 2,402 |
TMU | 1,635 |
PLT | 1,603 |
MET | 961 |
TXR | 648 |
FER | 302 |
FBT | 295 |
FTD | 262 |
BCQ | 156 |
The node-type values above are retained as published classification codes rather than expanded through an undocumented local mapping.
Sources and licence
| Dataset | Records | Extract | Imported | Licence |
|---|---|---|---|---|
DfT casualty severity aggregates 2024dft-road-casualties-aggregate-2024 | 128,272 | Not available | 25 July 2026 | Open Government Licence v3.0 |
DfT casualty severity aggregates 2025dft-road-casualties-aggregate-2025 | 60,991 | Not available | 25 July 2026 | Open Government Licence v3.0 |
Department for Transport road collisions 2024dft-road-collisions-2024 | 100,927 | Not available | 25 July 2026 | Open Government Licence v3.0 |
Department for Transport road collisions 2025dft-road-collisions-2025 | 48,472 | Not available | 25 July 2026 | Open Government Licence v3.0 |
DfT collision vehicle-type aggregates 2024dft-road-vehicles-aggregate-2024 | 182,154 | Not available | 25 July 2026 | Open Government Licence v3.0 |
DfT collision vehicle-type aggregates 2025dft-road-vehicles-aggregate-2025 | 87,128 | Not available | 25 July 2026 | Open Government Licence v3.0 |
Department for Transport annual average daily flowsdft-traffic-aadf | 600,551 | Not available | 25 July 2026 | Open Government Licence v3.0 |
Department for Transport road-traffic count pointsdft-traffic-count-points | 46,754 | Not available | 25 July 2026 | Open Government Licence v3.0 |
Department for Transport NaPTAN access nodesnaptan-access-nodes | 362,520 | Not available | 25 July 2026 | Open Government Licence v3.0 |
Company-level boundary
CompanyBeacon has registered-office postcodes in its Companies House projection, but this D1 estate does not contain a postcode-to-ONS-area lookup. The report therefore does not attach collision or transport measures to company profiles. A future company-geography feature should first import an official ONS Postcode Directory or National Statistics Postcode Lookup and retain the lookup vintage.