Skip to main content

77622

Details

AADF latest year 2016
Region Yorkshire and The Humber
Local authority East Riding of Yorkshire
Road name A614
Road type Major
Start junction road A161
End junction road Western Rd
Link length 1.10km (0.68 miles)
Easting & Northing 473640,424000
Latitude & longitude 53.70726,-0.88588

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
2016 Estimated using AADF from previous year on this link 14,850 11,939 2,353 319 132 110 129
2015 Estimated using AADF from previous year on this link 14,482 11,755 2,154 321 141 112 140
2014 Estimated using AADF from previous year on this link 14,166 11,527 2,054 328 152 127 130
2013 Estimated using AADF from previous year on this link 13,742 11,223 1,921 331 157 133 135
2012 Manual count 13,749 11,323 1,848 330 159 119 129
2011 Estimated using AADF from previous year on this link 12,353 9,622 2,142 476 201 35 78
2010 Estimated using AADF from previous year on this link 12,155 9,651 1,919 461 182 42 82
2009 Estimated using AADF from previous year on this link 12,066 9,709 1,797 444 181 44 72
2008 Estimated using AADF from previous year on this link 11,859 9,500 1,771 477 181 39 72
2007 Estimated using AADF from previous year on this link 12,049 9,713 1,735 477 161 41 83
2006 Estimated using AADF from previous year on this link 12,167 9,871 1,647 516 258 42 91
2005 Estimated using AADF from previous year on this link 12,375 10,062 1,622 544 165 49 98
2004 Estimated using AADF from previous year on this link 12,766 10,548 1,522 532 194 60 104
2003 Estimated using AADF from previous year on this link 12,460 10,412 1,382 449 240 91 126
2002 Manual count 12,739 10,812 1,273 460 269 64 130
2001 Estimated using AADF from previous year on this link 12,502 10,642 1,187 482 259 62 129
2000 Estimated using AADF from previous year on this link 12,857 10,982 1,179 514 270 59 123

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 77622 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 77622 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. 17
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. 34
Raw counts Vehicle counts recorded at this count point. 48

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