Skip to main content

58124

Details

AADF latest year 2017
Region West Midlands
Local authority Wolverhampton
Road name A41
Road type Major
Start junction road A4126
End junction road Ring Road Wolverhampton
Link length 1.90km (1.18 miles)
Easting & Northing 392000,298300
Latitude & longitude 52.58246,-2.11949

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
2017 Estimated using AADF from previous year on this link 20,058 15,716 3,233 581 37 110 418
2016 Estimated using AADF from previous year on this link 20,037 15,833 3,071 577 38 108 448
2015 Estimated using AADF from previous year on this link 19,565 15,590 2,812 570 41 111 483
2014 Estimated using AADF from previous year on this link 19,127 15,287 2,681 584 44 126 449
2013 Manual count 18,560 14,883 2,507 572 45 131 466
2012 Estimated using AADF from previous year on this link 18,414 14,058 3,509 391 57 77 380
2011 Estimated using AADF from previous year on this link 18,565 14,281 3,468 387 60 80 349
2010 Estimated using AADF from previous year on this link 18,267 14,324 3,107 372 55 94 370
2009 Estimated using AADF from previous year on this link 18,108 14,410 2,909 364 55 98 327
2008 Estimated using AADF from previous year on this link 17,774 14,100 2,866 389 55 88 331
2007 Estimated using AADF from previous year on this link 18,086 14,417 2,807 390 50 92 380
2006 Estimated using AADF from previous year on this link 18,252 14,652 2,666 419 80 97 418
2005 Manual count 18,573 14,936 2,627 448 50 111 451
2004 Estimated using AADF from previous year on this link 18,925 14,879 2,974 698 34 55 319
2003 Estimated using AADF from previous year on this link 18,460 14,687 2,701 598 42 84 390
2002 Manual count 18,800 15,252 2,487 601 47 59 401
2001 Estimated using AADF from previous year on this link 15,907 12,170 2,537 781 102 115 304
2000 Manual count 16,286 12,559 2,519 808 107 110 290

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 58124 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 58124 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. 18
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.