Skip to main content

17342

Details

AADF latest year 2018
Region Yorkshire and The Humber
Local authority Barnsley
Road name A635
Road type Major
Start junction road LA Boundary
End junction road B6428 Barugh Lane
Link length 6.30km (3.91 miles)
Easting & Northing 430000,408040
Latitude & longitude 53.56813,-1.54849

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 Estimated using AADF from previous year on this link 7,499 6,082 1,150 168 13 39 60
2017 Estimated using AADF from previous year on this link 7,477 6,112 1,098 165 13 39 63
2016 Estimated using AADF from previous year on this link 7,422 6,119 1,037 160 13 41 65
2015 Estimated using AADF from previous year on this link 7,267 6,044 961 156 13 41 66
2014 Estimated using AADF from previous year on this link 7,273 6,116 897 153 13 42 64
2013 Manual count 7,116 6,032 835 146 17 41 63
2012 Estimated using AADF from previous year on this link 6,676 5,520 828 159 30 77 93
2011 Estimated using AADF from previous year on this link 6,800 5,679 789 155 32 83 94
2010 Estimated using AADF from previous year on this link 6,722 5,662 745 149 36 76 90
2009 Estimated using AADF from previous year on this link 6,818 5,772 724 149 36 86 87
2008 Estimated using AADF from previous year on this link 6,886 5,842 711 163 32 83 87
2007 Estimated using AADF from previous year on this link 7,109 6,067 711 169 32 83 79
2006 Estimated using AADF from previous year on this link 7,184 6,229 645 154 32 83 73
2005 Manual count 7,005 6,060 614 154 34 99 78
2004 Estimated using AADF from previous year on this link 6,299 5,612 384 168 17 89 46
2003 Estimated using AADF from previous year on this link 6,288 5,607 381 160 17 86 54
2002 Manual count 6,178 5,557 338 161 20 70 52
2001 Estimated using AADF from previous year on this link 6,257 5,483 529 155 7 43 47
2000 Manual count 6,220 5,466 512 155 8 39 48

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 17342 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 17342 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. 38
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.