Skip to main content

57855

Details

AADF latest year 2024
Region Yorkshire and The Humber
Local authority North Yorkshire
Road name A64
Road type Major
Start junction road A659
End junction road LA Boundary
Link length 4.90km (3.04 miles)
Easting & Northing 454193,446771
Latitude & longitude 53.91428,-1.17645

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 Manual count 56,074 43,524 9,322 2,839 14 153 235
2023 Manual count 59,433 46,348 9,706 2,999 9 180 200
2022 Estimated using AADF from previous year on this link 62,089 48,960 9,089 3,611 21 216 213
2021 Manual count 54,660 42,446 8,297 3,529 23 188 199
2020 Automatic counter 45,324 35,404 6,770 2,774 13 189 186
2019 Manual count 67,378 54,518 8,802 3,413 13 331 314
2018 Automatic counter 59,390 46,828 9,208 2,853 51 240 261
2017 Manual count 61,069 48,560 9,089 2,907 52 236 278
2016 Estimated using AADF from previous year on this link 63,129 51,156 7,580 3,789 37 221 383
2015 Manual count 60,942 49,670 7,019 3,665 31 213 375
2014 Manual count 55,716 44,496 7,527 2,878 79 484 330
2013 Manual count 54,987 44,593 6,745 3,100 28 227 322
2012 Manual count 52,696 42,668 6,475 2,530 64 572 451
2011 Manual count 60,818 50,486 6,792 3,013 30 210 317
2010 Manual count 51,105 41,720 6,468 2,439 15 153 325
2009 Manual count 51,938 42,903 5,880 2,662 23 208 285
2008 Manual count 49,425 39,812 5,804 3,054 49 365 390
2007 Manual count 53,002 43,318 5,555 3,579 21 248 302
2006 Estimated using AADF from previous year on this link 47,389 38,401 5,668 2,800 27 168 352
2005 Manual count 46,978 38,401 5,278 2,807 28 170 322
2004 Manual count 48,368 39,193 5,382 3,393 2 157 243
2003 Manual count 49,704 40,796 5,481 2,799 18 339 289
2002 Manual count 48,545 40,753 4,204 2,928 14 238 422
2001 Manual count 52,043 43,156 5,227 3,090 9 235 335
2000 Manual count 47,180 38,459 4,922 3,083 60 391 325

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 57855 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 57855 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. 50
Raw counts Vehicle counts recorded at this count point. 480

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