Skip to main content
Road traffic statistics

56698

Details

AADF latest year 2019
Region East Midlands
Local authority Lincolnshire
Road name A151
Road type Major
Start junction road A15
End junction road Monks House Lane, Spalding
Link length 17.00km (10.56 miles)
Easting & Northing 520000,324500
Latitude & longitude 52.80473,-0.22133

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 5,643 4,301 988 318 3 23 13
2018 Estimated using AADF from previous year on this link 5,635 4,291 992 317 2 21 14
2017 Estimated using AADF from previous year on this link 5,607 4,312 947 312 3 22 14
2016 Manual count 5,554 4,317 895 305 3 23 15
2015 Estimated using AADF from previous year on this link 4,151 2,871 871 362 1 24 22
2014 Estimated using AADF from previous year on this link 4,043 2,827 820 350 1 25 21
2013 Estimated using AADF from previous year on this link 3,929 2,794 753 338 2 23 21
2012 Estimated using AADF from previous year on this link 3,858 2,785 702 330 2 22 19
2011 Estimated using AADF from previous year on this link 3,935 2,837 727 330 2 24 17
2010 Estimated using AADF from previous year on this link 3,911 2,857 693 320 2 24 17
2009 Estimated using AADF from previous year on this link 4,007 2,967 676 323 2 26 15
2008 Estimated using AADF from previous year on this link 3,945 2,949 627 330 2 24 15
2007 Manual count 3,971 3,000 600 332 2 24 15
2006 Estimated using AADF from previous year on this link 3,464 2,469 551 386 6 47 11
2005 Manual count 3,403 2,445 519 382 7 45 12
2004 Manual count 3,358 2,521 544 263 3 23 7
2003 Estimated using AADF from previous year on this link 3,686 2,693 639 274 0 72 8
2002 Manual count 3,533 2,597 586 286 0 56 8
2001 Estimated using AADF from previous year on this link 3,285 2,468 548 236 5 27 6
2000 Manual count 3,242 2,410 548 249 6 29 6

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 56698 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 56698 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. 144

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