Skip to main content

8677

Details

AADF latest year 2019
Region East Midlands
Local authority Lincolnshire
Road name A16
Road type Major
Start junction road A17
End junction road Tytton Lane East
Link length 8.50km (5.28 miles)
Easting & Northing 532076,341004
Latitude & longitude 52.95019,-0.03561

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
2019 Estimated using AADF from previous year on this link 18,626 14,142 2,967 1,365 35 120 32
2018 Estimated using AADF from previous year on this link 18,595 14,111 2,977 1,363 29 112 33
2017 Manual count 18,515 14,178 2,843 1,345 30 114 34
2016 Estimated using AADF from previous year on this link 15,801 11,585 2,835 1,247 22 100 35
2015 Estimated using AADF from previous year on this link 15,434 11,443 2,625 1,231 23 100 35
2014 Estimated using AADF from previous year on this link 15,241 11,523 2,411 1,172 23 100 35
2013 Estimated using AADF from previous year on this link 15,193 11,552 2,316 1,200 28 91 34
2012 Manual count 15,159 11,578 2,238 1,220 29 88 34
2011 Estimated using AADF from previous year on this link 15,487 11,617 2,262 1,404 31 164 40
2010 Manual count 15,536 11,688 2,203 1,456 35 150 39
2009 Estimated using AADF from previous year on this link 14,346 10,503 1,841 1,471 44 487 44
2008 Estimated using AADF from previous year on this link 14,496 10,534 1,845 1,591 39 483 43
2007 Manual count 14,796 10,881 1,778 1,637 39 459 41
2006 Estimated using AADF from previous year on this link 14,816 11,041 2,018 1,497 70 184 76
2005 Manual count 14,668 11,041 1,879 1,491 73 188 69
2004 Manual count 15,635 12,100 1,850 1,588 6 60 37
2003 Estimated using AADF from previous year on this link 15,745 12,106 2,000 1,451 35 164 24
2002 Manual count 15,340 11,951 1,783 1,428 42 151 27
2001 Manual count 14,616 11,166 2,074 1,236 61 103 37
2000 Manual count 12,609 9,513 1,742 1,150 65 141 63

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 8677 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 8677 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. 20
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. 40
Raw counts Vehicle counts recorded at this count point. 216

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