Skip to main content

1109

Details

AADF latest year 2019
Region Scotland
Local authority Stirling
Road name A811
Road type Major
Start junction road A875
End junction road B822
Link length 13.10km (8.14 miles)
Easting & Northing 262500,695400
Latitude & longitude 56.13144,-4.21389

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 7,286 5,243 1,453 479 4 35 77
2018 Estimated using AADF from previous year on this link 7,275 5,231 1,458 475 4 32 78
2017 Estimated using AADF from previous year on this link 7,229 5,256 1,392 466 4 33 82
2016 Estimated using AADF from previous year on this link 7,149 5,263 1,315 452 4 34 84
2015 Estimated using AADF from previous year on this link 6,972 5,198 1,218 437 4 34 85
2014 Estimated using AADF from previous year on this link 6,942 5,261 1,138 425 4 36 83
2013 Estimated using AADF from previous year on this link 6,775 5,188 1,059 412 5 34 81
2012 Estimated using AADF from previous year on this link 6,807 5,285 986 412 5 34 89
2011 Estimated using AADF from previous year on this link 6,917 5,438 940 412 5 37 90
2010 Estimated using AADF from previous year on this link 6,837 5,422 888 407 6 34 86
2009 Estimated using AADF from previous year on this link 6,912 5,527 863 401 6 38 83
2008 Manual count 7,000 5,594 847 440 5 36 83
2007 Estimated using AADF from previous year on this link 7,212 5,781 885 434 4 45 67
2006 Estimated using AADF from previous year on this link 7,248 5,936 802 404 3 45 61
2005 Manual count 7,058 5,774 765 400 4 54 65
2004 Manual count 6,421 5,405 601 299 0 52 64
2003 Estimated using AADF from previous year on this link 6,165 5,051 630 385 4 51 48
2002 Manual count 6,039 5,006 559 386 4 42 46
2001 Estimated using AADF from previous year on this link 6,571 5,518 548 376 5 71 58
2000 Manual count 6,531 5,501 530 376 5 64 60

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 1109 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 1109 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. 120

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