Skip to main content

56427

Details

AADF latest year 2017
Region London
Local authority City of London
Road name A1211
Road type Major
Start junction road Goodman's Yard
End junction road Bevis Marks
Link length 0.40km (0.25 miles)
Easting & Northing 533650,181000
Latitude & longitude 51.51213,-0.07539

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
2017 Estimated using AADF from previous year on this link 4,759 2,702 1,068 200 310 376 413
2016 Estimated using AADF from previous year on this link 4,778 2,703 1,077 206 317 363 430
2015 Estimated using AADF from previous year on this link 4,749 2,760 1,044 201 307 338 406
2014 Estimated using AADF from previous year on this link 4,669 2,609 1,087 214 325 325 434
2013 Manual count 4,546 2,523 1,043 212 324 320 447
2012 Estimated using AADF from previous year on this link 3,503 1,829 670 172 251 209 622
2011 Estimated using AADF from previous year on this link 3,699 1,991 684 160 248 219 645
2010 Estimated using AADF from previous year on this link 3,705 2,007 690 160 250 221 627
2009 Estimated using AADF from previous year on this link 3,761 2,069 717 152 230 235 588
2008 Estimated using AADF from previous year on this link 3,880 2,135 766 164 226 252 563
2007 Estimated using AADF from previous year on this link 4,000 2,215 818 167 231 270 530
2006 Estimated using AADF from previous year on this link 4,274 2,434 850 156 274 325 509
2005 Manual count 3,951 2,365 673 170 240 290 453
2004 Estimated using AADF from previous year on this link 5,765 3,465 1,105 137 704 619 439
2003 Estimated using AADF from previous year on this link 5,251 3,185 1,036 146 493 477 407
2002 Manual count 4,784 3,107 784 165 353 372 356
2001 Estimated using AADF from previous year on this link 5,067 3,045 902 157 263 362 601
2000 Estimated using AADF from previous year on this link 5,257 3,257 905 170 254 321 604

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 56427 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 56427 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. 18
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. 18
Raw counts Vehicle counts recorded at this count point. 36

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