According to exit polling in ten key states of the 2024 presidential election in the United States, ** percent of surveyed white voters reported voting for Donald Trump. In contrast, ** percent of Black voters reported voting for Kamala Harris.

As of late October 2024, young voter registration is lagging across a number of states when compared to the number registered on Election Day 2020. However, voter registration in swing states Michigan and Nevada increased by over 11 percent among 18 to 29-year-olds.

According to exit polling in ten key states of the 2024 presidential election in the United States, Donald Trump received the most support from white voters between the ages of ** and **. In comparison, ** percent of Black voters between the ages of ** and ** reported voting for Kamala Harris.

The table DE-Demographic-2025-07-24 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 761967 rows across 698 variables.

During the weeks leading up to the presidential election, early voting began in almost all states, with over ** million ballots being cast nationally as of Election Day. As of November *, more than half of mail-in and early in-person votes had been cast by women.

The table OR-Demographic-2025-07-02 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 3398746 rows across 698 variables.

In 2024, 80.5 percent of people aged between 65 and 74 years old were registered to vote in the United States - the highest share of any age group. In comparison, 58.3 percent of 18 to 24 year-olds were registered to vote in that year.

Election Data Attribute Field Definitions | Wisconsin Cities, Towns, & Villages Data Attributes Ward Data Overview: January 2025 municipal wards were collected in January 2025 by LTSB through LTSB's GeoData Collector. Current statutes require each county clerk, or board of election commissioners, no later than January 15 and July 15 of each year, to transmit to the LTSB, in an electronic format (approved by LTSB), a report confirming the boundaries of each municipality, ward and supervisory district within the county as of the preceding “snapshot” date of January 1 or July 1 respectively. Population totals for 2025 wards were estimated by aggregating 2020 US Census PL94-171 population data. LTSB has NOT topologically integrated the data. Election Data Overview: The 2024 Wisconsin election data that is included in this file was collected by LTSB from the *Wisconsin Elections Commission (WEC) after the general election. A disaggregation process was performed on this election data based on the municipal ward layer that was available at the time of the election. Disaggregation of Election Data: Election data is first disaggregated from reporting units to wards, and then to census blocks. Next, the election data is aggregated back up to wards, municipalities, and counties. The disaggregation of election data to census blocks is done based on total population. Detailed Methodology:Data is disaggregated first from reporting unit (i.e. multiple wards) to the ward level proportionate to the population of that ward.The data then is distributed down to the block level, again based on total population.When data is disaggregated to block or ward, we restrain vote totals not to exceed population 18 numbers, unless absolutely required.This methodology results in the following: Election data totals reported to the WEC at the state, county, municipal and reporting unit level should match the disaggregated election data total at the same levels. Election data totals reported to the WEC at ward level may not match the ward totals in the disaggregated election data file.Some wards may have more election data allocated than voter age population. This will occur if a change to the geography results in more voters than the 2020 historical population limits.Other things of note… We use a static, official ward layer (in this case created in 2025) to disaggregate election data to blocks. Using this ward layer creates some challenges. New wards are created every year due to annexations and incorporations. When these new wards are reported with election data, an issue arises wherein election data is being reported for wards that do not exist in our official ward layer. For example, if "Cityville" has four wards in the official ward layer, the election data may be reported for five wards, including a new ward from an annexation. There are two different scenarios and courses of action to these issues: When a single new ward is present in the election data but there is no ward geometry present in the official ward layer, the votes attributed to this new ward are distributed to all the other wards in the municipality based on population percentage. Distributing based on population percentage means that the proportion of the population of the municipality will receive that same proportion of votes from the new ward. In the example of Cityville explained above, the fifth ward may have five votes reported, but since there is no corresponding fifth ward in the official layer, these five votes will be assigned to each of the other wards in Cityville according the percentage of population.Another case is when a new ward is reported, but its votes are part of reporting unit. In this case, the votes for the new ward are assigned to the other wards in the reporting unit by population percentage; and not to wards in the municipality as a whole. For example, Cityville’s ward five was given as a reporting unit together with wards 1, 4, and 5. In this case, the votes in ward five are assigned to wards one and four according to population percentage. Outline Ward-by-Ward Election ResultsThe process of collecting election data and disaggregating to municipal wards occurs after a general election, so disaggregation has occurred with different ward layers and different population totals. We have outlined (to the best of our knowledge) what layer and population totals were used to produce these ward-by-ward election results.Election data disaggregates from WEC Reporting Unit -> Ward [Variant year outlined below]Elections 1990 – 2000: Wards 1991 (Census 1990 totals used for disaggregation)Elections 2002 – 2010: Wards 2001 (Census 2000 totals used for disaggregation)Elections 2012: Wards 2011 (Census 2010 totals used for disaggregation)Elections 2014 – 2016: Wards 2018 (Census 2010 totals used for disaggregation)Elections 2018: Wards 2018 (Census 2010 totals used for disaggregation)Elections 2020: Wards 2020 (Census 2020 totals used for disaggregation)Elections 2022: Wards 2022 (Census 2020 totals used for disaggregation)Elections 2024: Wards 2025 (Census 2020 totals used for disaggregation)Blocks -> Centroid geometry and spatially joined with Wards [All Versions]Each Block has an assignment to each of the ward versions outlined above.In the event that a ward exists now in which no block exists due to annexations, a block centroid was created with a population 0, and encoded with the proper Census IDs.Wards [All Versions] disaggregate -> Blocks This yields a block centroid layer that contains all elections from 1990 to 2024.Blocks [with all election data] -> Wards 2025 (then MCD 2025, and County 2025) All election data (including later elections) is aggregated to the Wards 2025 assignment of the blocks.Notes:Population of municipal wards 1991, 2001, 2011, 2020, 2022, and 2025 used for disaggregation were determined by their respective Census.Population and Election data will be contained within a county boundary. This means that even though MCD and ward boundaries vary greatly between versions of the wards, county boundaries have stayed the same, so data should total within a county the same between wards 2011 and wards 2025.Election data may be different for the same legislative district, for the same election, due to changes in the wards from 2011 and 2025. This is due to boundary corrections in the data from 2011 to 2025, and annexations, where a block may have been reassigned.*WEC replaced the previous Government Accountability Board (GAB) in 2016, which replaced the previous State Elections Board in 2008.

The table MN-Demographic-2025-07-28 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 3632926 rows across 698 variables.

Electoral registrations for parliamentary and local government elections as recorded in electoral registers for England, Wales, Scotland and Northern Ireland.

During the weeks leading up to the presidential election, early voting began in almost all states, with over ** million ballots being cast nationally as of Election Day. Although ** percent of mail-in and early in-person votes were cast by voters aged 65 or older, ** percent of those aged 18 to 29 years old voted early.

This data collection contains voter registration and turnout surveys. The files contain summaries at state, town, and county levels. Each level of data include: total population, total voting-age population, total voter registration (excluding ND, WI), total ballots cast, total votes cast for president, and voter registration by party. Note: see the documentation for information on missing data.

Dave Leip's website

The Dave Leip website here: https://uselectionatlas.org/BOTTOM/store_data.php lists the available data. Files are occasionally updated by Dave Leip, and new versions are made available, but CCSS is not notified. If you suspect the file you want may be updated, please get in touch with CCSS. These files were last updated on 9 JUL 2024.

Note that file version numbers are those assigned to them by Dave Leip's Election Atlas. Please refer to the Data and Reproduction Archive Version number in your citations for the full dataset.

For additional information on file layout, etc. see https://uselectionatlas.org/BOTTOM/DOWNLOAD/spread_turnout.html.

Similar data may be available at https://www.electproject.org/election-data/voter-turnout-data dating back to 1787.

The table MS-Demographic-2025-08-04 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 1950628 rows across 698 variables.

The table IA-Demographic-2025-06-16 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 2031252 rows across 698 variables.

According to exit polling in *** key states of the 2024 presidential election in the United States, almost ********** of voters who had never attended college reported voting for Donald Trump. In comparison, a similar share of voters with ******** degrees reported voting for Kamala Harris.

2024 Primary & General Elections VTDs Voting Tabulation Districts (VTDs), the census geographic equivalent of county election precincts, are created for the purpose of relating 2020 Census population data to election precinct data. VTDs can differ from actual election precincts because precincts do not always follow census geography. The VTDs currently included in the redistricting database closely correspond to the precincts in effect for the 2024 primary and general elections. On the occasion that a precinct is in two noncontiguous pieces, it is a suffixed VTD in the database. For example, if precinct 0001 had two non-contiguous areas, the corresponding VTD would be VTD 0001A and VTD 0001B. If an election precinct does not match any census geography, it is consolidated with an adjacent precinct and given that precinct's corresponding VTD number. There are 9,712 VTDs in the 2024 primary & general elections VTDs shapefile. GIS users can join the council's redistricting election datasets to the 2024 primary & general elections VTDs shapefile in this directory. Use the common field name 'VTDKEY' to join the data. GIS users can join 2020 Census population data (VTDs_24PG_Pop.zip) to the 2024 primary & general elections VTDs shapefile in this directory. Use the common field name 'VTDKEY' to join the data. The VTDs shapefile (.shp) is in a compressed file (.zip) format: VTDs_24PG.zip - 2024 Primary & General Elections VTDs CNTY (num) - County FIPS Census code COLOR (num) - Color assignment for symbology VTD (txt) - VTD name (2024 general election) CNTYKEY (num) - Unique code used to join to geographic data VTDKEY (num) - Unique code used to join to geographic data CNTYVTD (txt) - Unique code used to join geographic data (CNTYKEY + VTD) The population data file contains the 2020 Census population by VTD as comma-separated values: VTDs_24PG_Pop.zip (.txt file in compressed format) - 2024 primary & general elections VTD, 2020 Census population CountyFIPS (txt) - County FIPS Census Code County (txt) - County name CNTY (num) - County FIPS Census Code VTD (txt) - VTD name (2024 general election) CNTYVTD (txt) - Unique code used to join geographic data (CNTY + VTD) VTDKEY (num) - Unique code used to join to geographic data total (num) - Total Population

2024 Voter Registration Statistics (Geographical Constituencies, Functional Constituencies and Election Committee Subsectors)

The table SD-Demographic-2025-07-15 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 601438 rows across 698 variables.

The table CO-Demographic-2025-08-01 is part of the dataset L2 Voter and Demographic Dataset, available at https://stanford.redivis.com/datasets/t6qv-ad1vt3wqf. It contains 4022482 rows across 698 variables.

Voting data for the November 2024 election in Roanoke County, Virginia, by voting district. Includes presidential, Senate, House of Representatives, and Town of Vinton results. Data from here.