Skip to main content

7240

Details

AADF latest year 2018
Region West Midlands
Local authority Staffordshire
Road name A522
Road type Major
Start junction road A52
End junction road Park Drive, Cheadle
Link length 3.50km (2.17 miles)
Easting & Northing 400000,344550
Latitude & longitude 52.99829,-2.00145

Location

Contents

Average Annual Daily Flow

Average annual daily flow
Year Count method All motor vehicles Cars & taxis LGVs HGVs Pedal cycles Motorcycles Buses & coaches
2018 Manual count 7,505 6,210 827 404 30 36 27
2017 Estimated using AADF from previous year on this link 8,241 6,429 1,297 406 21 79 31
2016 Estimated using AADF from previous year on this link 8,169 6,437 1,226 394 20 81 32
2015 Estimated using AADF from previous year on this link 7,983 6,358 1,135 377 21 81 32
2014 Estimated using AADF from previous year on this link 7,984 6,434 1,061 373 21 85 31
2013 Estimated using AADF from previous year on this link 7,810 6,345 987 365 26 82 31
2012 Estimated using AADF from previous year on this link 7,859 6,464 919 361 26 81 33
2011 Estimated using AADF from previous year on this link 8,002 6,651 876 353 28 88 34
2010 Estimated using AADF from previous year on this link 7,914 6,631 828 343 32 80 32
2009 Estimated using AADF from previous year on this link 8,021 6,759 805 337 31 90 30
2008 Manual count 8,115 6,841 790 368 27 86 30
2007 Estimated using AADF from previous year on this link 7,394 5,755 1,065 445 17 59 70
2006 Estimated using AADF from previous year on this link 7,403 5,908 966 405 17 59 65
2005 Estimated using AADF from previous year on this link 7,208 5,747 920 402 18 70 69
2004 Manual count 7,187 5,753 877 413 17 76 68
2003 Estimated using AADF from previous year on this link 7,717 6,278 916 336 17 113 74
2002 Manual count 7,535 6,222 813 337 21 92 71
2001 Estimated using AADF from previous year on this link 10,939 8,562 1,355 797 6 107 118
2000 Estimated using AADF from previous year on this link 10,846 8,536 1,310 783 7 96 121

Download data

Data disclaimer

Traffic figures at the regional and national level are robust, and are reported as accredited official statistics. However, DfT’s traffic estimates for individual road links and small areas are less robust, as they are not always based on up-to-date counts made at these locations. Where other more up-to-date sources of traffic data are available (e.g. from local highways authorities), this may provide a more accurate estimate of traffic at these locations.

It is the responsibility of the user to decide which data are most appropriate for their purpose, and if DfT road link level traffic estimates are used, to make a note of the limitations in any published material.

Quality flags in data downloads

DfT’s road link level traffic estimates are calculated using a variety of methods, with some methods likely to produce more accurate estimates than others.

The data tables available to download here contain a column - estimation_method – showing the method used to estimate traffic for each location and year. Figures having an estimation method of “Counted” are likely to be more accurate than those marked as “Estimated”, and the latter should be used with caution.

Site details
Manual count point site 7240 details
Average annual daily flow
Number of vehicles that travel past the count point (in both directions) on an average day of the year.
Average annual daily flow by direction
Number of vehicles that travel past the count point on an average day of the year, by direction of travel.
Raw counts
Vehicle counts recorded at this count point.
Data Description Records Download
Site details Manual count point site 7240 details 1
Average annual daily flow Number of vehicles that travel past the count point (in both directions) on an average day of the year. 19
Average annual daily flow by direction Number of vehicles that travel past the count point on an average day of the year, by direction of travel. 36
Raw counts Vehicle counts recorded at this count point. 96

To apply more filters to downloads, or retrieve data split into pages you can use our API.