Skip to main content

75141

Details

AADF latest year 2024
Region South East
Local authority Surrey
Road name A247
Road type Major
Start junction road A247 Clandon Rd
End junction road A3
Link length 0.30km (0.19 miles)
Easting & Northing 504172,154333
Latitude & longitude 51.27862,-0.50783

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
2024 Estimated from nearby links 5,320 3,848 1,147 253 0 64 8
2023 Estimated from nearby links 5,257 3,820 1,116 251 0 63 8
2022 Estimated from nearby links 5,170 3,764 1,080 254 0 64 8
2021 Estimated from nearby links 3,689 2,771 724 158 0 30 7
2020 Estimated from nearby links 3,156 2,141 832 157 0 25 1
2019 Estimated from nearby links 4,811 3,822 763 164 0 47 16
2018 Estimated from nearby links 4,929 3,969 732 161 0 50 16
2017 Estimated from nearby links 4,905 3,982 699 159 0 48 17
2016 Estimated from nearby links 4,987 3,977 748 202 0 51 10
2015 Estimated from nearby links 4,807 3,861 693 194 0 49 10
2014 Estimated from nearby links 4,665 3,784 646 167 1 58 10
2013 Estimated from nearby links 4,278 3,413 646 158 0 52 9
2012 Estimated from nearby links 4,100 3,300 577 159 0 54 11
2011 Estimated from nearby links 4,424 3,615 596 156 0 49 8
2010 Estimated from nearby links 4,548 3,775 567 146 0 43 17
2009 Estimated from nearby links 4,143 3,449 471 170 0 43 10
2008 Estimated from nearby links 4,475 3,671 601 157 0 35 11
2007 Estimated from nearby links 4,411 3,619 569 167 0 46 10
2006 Estimated from nearby links 4,380 3,645 514 165 0 46 10
2005 Estimated from nearby links 4,569 3,749 539 190 0 80 11
2004 Estimated from nearby links 4,821 3,994 540 206 0 66 15
2003 Estimated from nearby links 4,694 3,928 485 198 0 65 18
2002 Estimated from nearby links 4,609 3,942 419 184 0 48 16
2001 Estimated from nearby links 4,492 3,831 416 183 0 47 15
2000 Estimated from nearby links 4,044 3,376 442 174 0 38 14

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 75141 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 75141 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. 25
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. 25
Raw counts Vehicle counts recorded at this count point. 0

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