Skip to main content

17636

Details

AADF latest year 2019
Region London
Local authority Hillingdon
Road name A4180
Road type Major
Start junction road A40(T)
End junction road B466 Ickenham Rd
Link length 3.70km (2.30 miles)
Easting & Northing 510000,186200
Latitude & longitude 51.56396,-0.41443

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 17,019 14,466 1,890 219 108 236 208
2018 Manual count 16,972 14,428 1,891 219 115 224 209
2017 Estimated using AADF from previous year on this link 14,757 11,804 1,820 454 117 386 293
2016 Estimated using AADF from previous year on this link 14,788 11,808 1,836 467 120 372 305
2015 Estimated using AADF from previous year on this link 14,921 12,057 1,780 450 116 347 288
2014 Estimated using AADF from previous year on this link 14,924 12,097 1,710 449 101 366 301
2013 Estimated using AADF from previous year on this link 14,860 12,063 1,655 475 90 354 314
2012 Estimated using AADF from previous year on this link 14,733 11,958 1,614 458 110 362 340
2011 Estimated using AADF from previous year on this link 14,948 12,191 1,653 426 127 333 345
2010 Estimated using AADF from previous year on this link 14,977 12,228 1,662 418 127 335 334
2009 Estimated using AADF from previous year on this link 15,335 12,567 1,680 417 132 357 314
2008 Manual count 15,517 12,669 1,724 448 122 378 298
2007 Manual count 18,321 14,909 2,443 305 86 458 206
2006 Manual count 19,664 16,333 2,180 401 130 500 250
2005 Manual count 20,708 17,800 1,898 555 32 275 180
2004 Manual count 20,074 16,591 2,253 575 58 466 189
2003 Manual count 21,016 17,423 2,412 600 96 380 201
2002 Manual count 21,701 18,840 1,851 445 107 314 251
2001 Manual count 20,143 17,013 2,013 433 102 340 344
2000 Estimated using AADF from previous year on this link 20,196 17,529 1,822 309 250 347 189

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 17636 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 17636 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.