Skip to main content
Road traffic statistics

16137

Details

AADF latest year 2016
Region East of England
Local authority Central Bedfordshire
Road name A5
Road type Major
Start junction road A5120
End junction road A505
Link length 1.30km (0.81 miles)
Easting & Northing 501630,222175
Latitude & longitude 51.88888,-0.52464

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
2016 Estimated using AADF from previous year on this link 16,573 12,012 3,207 899 272 87 367
2015 Estimated using AADF from previous year on this link 15,938 11,663 2,970 862 229 84 360
2014 Estimated using AADF from previous year on this link 15,590 11,437 2,832 893 246 95 334
2013 Estimated using AADF from previous year on this link 15,125 11,135 2,648 896 254 99 347
2012 Estimated using AADF from previous year on this link 15,090 11,234 2,548 888 257 89 332
2011 Estimated using AADF from previous year on this link 15,230 11,412 2,518 902 272 93 305
2010 Estimated using AADF from previous year on this link 15,009 11,447 2,256 874 246 110 322
2009 Manual count 14,881 11,516 2,113 852 244 116 284
2008 Estimated using AADF from previous year on this link 14,920 11,179 2,331 1,068 134 135 207
2007 Estimated using AADF from previous year on this link 15,181 11,430 2,283 1,088 119 142 238
2006 Estimated using AADF from previous year on this link 15,367 11,616 2,168 1,172 191 149 262
2005 Estimated using AADF from previous year on this link 15,692 11,841 2,135 1,262 122 171 283
2004 Manual count 16,182 12,412 2,003 1,259 144 208 300
2003 Estimated using AADF from previous year on this link 14,161 10,623 1,904 1,159 208 167 308
2002 Manual count 14,396 11,031 1,753 1,179 233 117 316
2001 Estimated using AADF from previous year on this link 18,939 13,764 2,755 1,490 121 252 678
2000 Estimated using AADF from previous year on this link 19,411 14,205 2,736 1,582 127 241 647

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 16137 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 16137 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. 17
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. 34
Raw counts Vehicle counts recorded at this count point. 72

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