CrashDNA

Crash data.
Real-world context.

Explore CrashDNA
Texas / City guides
PUBLIC DATA. LOCAL CONTEXT.

Anthony Crash Guide.

El Paso County

Reported crash counts, locations and trends in Anthony.

Records through 2026-09-30 Source: TxDOT public records Prepared 2026-10-17

Choose a period, then select Update guide.

Guide figures: Oct 1, 2025 to Sep 30, 2026. Based on records available through Sep 30, 2026. The map uses a separate calendar year.

Reported crashes164 6.5% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes2 2 more2 vs. 0
Compared with Oct 1, 2024 to Sep 30, 2025
People killed2 2 more2 vs. 0
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured1 3 fewer1 vs. 4
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 6.5%.

Compared with Oct 1, 2024 to Sep 30, 2025. Counts alone do not tell us how risky a trip is.

Explore the data →
KNOW THE PLACE

Getting around Anthony

Anthony is a town in El Paso County, Texas. Include the place and county when looking up local road notices, especially where another Texas community shares the same name. [1]

Location context, separate from the crash analysis below. Local road descriptions are added only after source review.

Local context sources
  1. U.S. Census Bureau · Texas place/county reference (2026)
  2. TxDOT · how to use DriveTexas for current conditions
THE LOCAL PICTURE

Anthony’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 164 reported crashes in Anthony. That is 10 more than the 154 recorded for the corresponding dates a year earlier—a 6.5% increase in reported crashes.

Interstate 10 appears repeatedly in the reports, with 14 crashes listed under that road name. The 11 a.m. hour had the highest reported count among crashes with a recorded time, accounting for 14 of the 164 crashes in this guide.

Based on the public TxDOT records included in this guide. Counts describe reported crashes, not risk per trip or why a crash happened. Source, coverage and limitations →

WHERE IT HAPPENS

Explore Anthony’s reported crash locations.

Named areas with the most matching crashes. Choose an area to zoom in.

  1. The ranked areas appear when the map loads.
View the area data ↓

Approximate areas, not verified intersections. The list follows the map filters.

This map uses a calendar year, not the guide’s reporting period. The figures above cover Oct 1, 2025 to Sep 30, 2026 (164 crashes). The count below follows the selected map year and filters.

Loading crash map…

Loading the 2026 map. Records are available through 2026-09-30.

Background map: OpenStreetMap. Map tiles load automatically; your browser sends the provider your IP address and the requested map area.

Map area data & how locations are grouped

Numbers on markers are crash counts. Areas use a 0.002° grid (roughly 180–220 metres across in Texas), not verified intersections. Names use the most common recorded street or intersection-pair label in each area across the loaded history; they are not verified neighborhood boundaries. Several areas may share a road name. Missing-coordinate records remain in the totals.

THE LONGER VIEW

The same month, year over year

Compare seasonal patterns across 2022–2026. Each line is one year. Hollow points and dashed segments mark partial months; gaps are not treated as zero. Historical context stays visible when you change the guide’s reporting period.

20222023202420252026
06121723JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 8 reported crashesFeb 2022: 19 reported crashesMar 2022: 15 reported crashesApr 2022: 9 reported crashesMay 2022: 15 reported crashesJun 2022: 11 reported crashesJul 2022: 17 reported crashesAug 2022: 5 reported crashesSep 2022: 11 reported crashesOct 2022: 8 reported crashesNov 2022: 5 reported crashesDec 2022: 9 reported crashesJan 2023: 4 reported crashesFeb 2023: 8 reported crashesMar 2023: 15 reported crashesApr 2023: 11 reported crashesMay 2023: 13 reported crashesJun 2023: 13 reported crashesJul 2023: 11 reported crashesAug 2023: 10 reported crashesSep 2023: 10 reported crashesOct 2023: 5 reported crashesNov 2023: 3 reported crashesDec 2023: 7 reported crashesJan 2024: 6 reported crashesFeb 2024: 7 reported crashesMar 2024: 19 reported crashesApr 2024: 12 reported crashesMay 2024: 12 reported crashesJun 2024: 11 reported crashesJul 2024: 11 reported crashesAug 2024: 14 reported crashesSep 2024: 5 reported crashesOct 2024: 11 reported crashesNov 2024: 16 reported crashesDec 2024: 11 reported crashesJan 2025: 17 reported crashesFeb 2025: 13 reported crashesMar 2025: 13 reported crashesApr 2025: 8 reported crashesMay 2025: 11 reported crashesJun 2025: 12 reported crashesJul 2025: 15 reported crashesAug 2025: 10 reported crashesSep 2025: 17 reported crashesOct 2025: 13 reported crashesNov 2025: 17 reported crashesDec 2025: 14 reported crashesJan 2026: 17 reported crashesFeb 2026: 11 reported crashesMar 2026: 23 reported crashesApr 2026: 9 reported crashesMay 2026: 14 reported crashesJun 2026: 19 reported crashesJul 2026: 8 reported crashesAug 2026: 9 reported crashesSep 2026: 10 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan8461717
Feb19871311
Mar1515191323
Apr9111289
May1513121114
Jun1113111219
Jul171111158
Aug51014109
Sep111051710
Oct851113—
Nov531617—
Dec971114—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Anthony recorded 120 crashes, compared with 116 over the matching dates a year earlier. That is 3.4% more reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 11 AM.

Oct 1, 2025 to Sep 30, 2026 · Known hours only.

Time of day

071412 AM: 1 reported crash12 AM1 AM: 2 reported crashes2 AM: 3 reported crashes3 AM: 4 reported crashes3 AM4 AM: 0 reported crashes5 AM: 3 reported crashes6 AM: 6 reported crashes6 AM7 AM: 6 reported crashes8 AM: 10 reported crashes9 AM: 13 reported crashes9 AM10 AM: 4 reported crashes11 AM: 14 reported crashes12 PM: 9 reported crashes12 PM1 PM: 10 reported crashes2 PM: 13 reported crashes3 PM: 13 reported crashes3 PM4 PM: 12 reported crashes5 PM: 11 reported crashes6 PM: 7 reported crashes6 PM7 PM: 6 reported crashes8 PM: 5 reported crashes9 PM: 3 reported crashes9 PM10 PM: 6 reported crashes11 PM: 3 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM1000
1 AM2000
2 AM3000
3 AM4000
4 AM0000
5 AM3000
6 AM6000
7 AM6000
8 AM10000
9 AM13110
10 AM4000
11 AM14000
12 PM9000
1 PM10000
2 PM13000
3 PM13000
4 PM12000
5 PM11000
6 PM7000
7 PM6001
8 PM5000
9 PM3000
10 PM6000
11 PM3110

Day of the week

01529Sun: 24 reported crashesSun24Mon: 25 reported crashesMon25Tue: 16 reported crashesTue16Wed: 19 reported crashesWed19Thu: 29 reported crashesThu29Fri: 29 reported crashesFri29Sat: 22 reported crashesSat22
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun24001
Mon25000
Tue16000
Wed19000
Thu29110
Fri29000
Sat22110

Month by month

012232025-10: 13 reported crashes10/252025-11: 17 reported crashes2025-12: 14 reported crashes12/252026-01: 17 reported crashes2026-02: 11 reported crashes02/262026-03: 23 reported crashes2026-04: 9 reported crashes04/262026-05: 14 reported crashes2026-06: 19 reported crashes06/262026-07: 8 reported crashes2026-08: 9 reported crashes08/262026-09: 10 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-1013000
2025-1117110
2025-1214001
2026-0117000
2026-0211000
2026-0323000
2026-049110
2026-0514000
2026-0619000
2026-078000
2026-089000
2026-0910000

Selected period; * partial month. Outlined bars mean missing coverage, not zero crashes.

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved53
  • Commercial vehicle involved44
  • Pedestrian involved4
  • Bicycle involved0
  • Motorcycle involved0

Crash counts, not people. Categories overlap—a crash can appear in more than one group.

View involvement & severity details

People killed or injured are totals for the whole crash, not necessarily people in the named travel mode.

Crash involvement categories; do not sum these rows
GroupCrashesFatal crashesPeople killedPeople seriously injured
Truck / truck-tractor involved53220
Commercial vehicle involved44220
Pedestrian involved4001
Bicycle involved0000
Motorcycle involved0000
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. Interstate 1014 crashes
  2. South Main Street12 crashes
  3. Antonio Street11 crashes
  4. Antonio8 crashes
  5. Farm-to-Market Road 19055 crashes

Oct 1, 2025 to Sep 30, 2026. Counts, not the chance of a crash on a trip. Street-name variants may split the same corridor. Short road labels are expanded for readability; the tables and CSV preserve recorded labels.

View all road rankings
Top 20 reported road labels by crash count
GroupCrashesFatal crashesPeople killedPeople seriously injured
IH 1014000
S MAIN ST12001
ANTONIO ST11110
ANTONIO8000
FM 19055000
S DESERT BLVD5000
W INTERSTATE 105000
FRANKLIN ST4000
N DESERT BLVD4000
WILDCAT DR4000
N DESERT3000
S DESERT3000
S MAIN3000
W IH 103000
DONIPHAN DR2000
E I102000
E IH 102000
E INTERSTATE FWY2000
E INTERSTATE HWY2000
INTERSTATE 10 HWY2000
Reported intersection pairs

Only records flagged as intersections with both street names. These are reported labels—not verified geographic intersections.

Top 20 reported street pairs by crash count
GroupCrashesFatal crashesPeople killedPeople seriously injured
ANTONIO ST & WILDCAT DR3110
ANTONIO ST & N DESERT BLVD2000
ANTONIO ST & S DESERT BLVD2000
FM 1905 & SS 62000
3RD ST & JEFFERSON1000
6TH ST & POPLAR ST1000
ANTONIO & N DESERT1000
ANTONIO & SANDIA1000
ANTONIO ST & DEBRA RD1000
ANTONIO ST & EXIT 0 ANTHONY1000
ANTONIO ST & S DESERT RD1000
E ANTONIO ST & S DESERT BLVD1000
E WASHINGTON ST & N N MAIN RD1000
FM 1905 & SH 201000
FRANKLIN ST & S MAIN1000
FRANKLIN ST & S MAIN ST1000
MOUNTAIN PASS & N DESERT BLVD1000
MOUNTAIN PASS & NORTH DESERT1000
N DESERT RD & W ANTONIO ST1000
S MAIN & W WASHINGTON RD1000
SOURCE & ATTRIBUTION

Cite this guide.

Using these figures? Keep the reporting period and source with them.

CrashDNA. Anthony Crash Guide. Anthony — El Paso County, Texas. All reported crashes; selected reporting period 2025-10-01–2026-09-30. Analysis of available public Texas Department of Transportation (TxDOT) crash records. Snapshot prepared 2026-10-17. https://crashdna.com/texas/anthony/

You can also select and copy the citation text above. Figures describe available records, not traffic-adjusted risk or independently verified complete reporting.

Methods, definitions and limitations

Anthony town · El Paso County. Reported city code 16; county codes 71. Current Census place identifier 4803432 (2026 reference). These identifiers reconcile the reported source labels, not independently geocoded historical boundaries.

Source: public Texas Department of Transportation (TxDOT) crash records loaded for this publication. Guide focus: All reported crashes. All displayed totals, historical comparisons, maps, rankings and CSV rows use this cohort. Selected reporting period: exact recorded city label ANTHONY, Oct 1, 2025 to Sep 30, 2026. Each crash is counted once using its selected current record revision. This is not a metropolitan-area or police-agency-only filter.

Fatal crashes count events; deaths and serious injuries count people. Fatal and serious-injury crash groups use recorded severity codes 4 and 1. A crash can involve multiple vehicle or road-user types. Counts do not control for traffic or pedestrian activity, do not establish fault, and are not crash rates.

In the selected reporting period, 48 records lack usable Texas-range coordinates for Oct 1, 2025 to Sep 30, 2026 (the guide period, not the separate map year); 0 lack a usable hour; 17 lack a usable road label. 138 records are not assigned a usable intersection pair (including non-intersection crashes). Unknown categories remain in totals but not narrative rankings. Coordinates are not independently verified.

Latest 12 months means the latest available calendar month plus the preceding 11 months, clipped to loaded coverage; an unfinished final month is partial. Year to date means January 1 through the latest loaded date in that year, not through today. Historical charts and the map use the wider loaded history (Jan 1, 2022 to Sep 30, 2026); the monthly year-over-year chart shows up to five recent years. Map year, crash-type and outcome filters apply only to the map and its linked area table. Every matching record with coordinates contributes; there is no top-100 cap. Map locations are approximate grid centres, not exact crash sites. Area names use reported road labels, not verified neighborhoods. CSV contains aggregate tables, not individual crash records.

Loaded extraction intervals span the selected period. Source intervals do not guarantee complete reporting. New reports and amendments can change earlier months. Prepared 2026-10-17T22:02:46.037Z. Approved snapshots change only after an editor publishes an update.

Source extraction intervals
  • 2022-01-01 – 2022-03-01 · extracted 20260910100040
  • 2022-03-02 – 2022-04-26 · extracted 20260910100040
  • 2022-04-27 – 2022-06-22 · extracted 20260910100040
  • 2022-06-23 – 2022-08-22 · extracted 20260910100040
  • 2022-08-23 – 2022-10-16 · extracted 20260910100040
  • 2022-10-17 – 2022-12-08 · extracted 20260910100040
  • 2022-12-09 – 2022-12-31 · extracted 20260910100040
  • 2023-01-01 – 2023-02-27 · extracted 20260910100112
  • 2023-02-28 – 2023-04-24 · extracted 20260910100112
  • 2023-04-01 – 2023-04-24 · extracted 20260910100112
  • 2023-04-25 – 2023-06-19 · extracted 20260910100112
  • 2023-06-20 – 2023-08-17 · extracted 20260910100112
  • 2023-08-18 – 2023-10-12 · extracted 20260910100112
  • 2023-10-13 – 2023-12-05 · extracted 20260910100112
  • 2023-12-06 – 2023-12-31 · extracted 20260910100112
  • 2024-01-01 – 2024-02-29 · extracted 20260828124847
  • 2024-03-01 – 2024-04-26 · extracted 20260828124847
  • 2024-04-27 – 2024-06-22 · extracted 20260828124847
  • 2024-06-23 – 2024-08-22 · extracted 20260828124847
  • 2024-08-23 – 2024-10-16 · extracted 20260828124847
  • 2024-10-17 – 2024-12-09 · extracted 20260828124847
  • 2024-12-10 – 2024-12-31 · extracted 20260828124847
  • 2025-01-01 – 2025-03-05 · extracted 20260910100224
  • 2025-03-06 – 2025-05-01 · extracted 20260910100224
  • 2025-05-02 – 2025-06-29 · extracted 20260910100224
  • 2025-06-30 – 2025-08-29 · extracted 20260910100224
  • 2025-08-30 – 2025-10-23 · extracted 20260910100224
  • 2025-10-24 – 2025-12-16 · extracted 20260910100224
  • 2025-12-17 – 2025-12-31 · extracted 20260910100224
  • 2026-01-01 – 2026-03-03 · extracted 20260910100333
  • 2026-03-04 – 2026-04-30 · extracted 20260910100333
  • 2026-05-01 – 2026-06-27 · extracted 20260910100333
  • 2026-06-28 – 2026-08-29 · extracted 20260910100333
  • 2026-08-30 – 2026-08-31 · extracted 20260910100333
  • 2026-09-01 – 2026-09-30 · extracted 20261010194744

Download selected-period CSV · Download all-history CSV

CSV download
A table file you can open in a spreadsheet. Downloads contain grouped counts, not individual crash reports.
Crash count versus risk
A count tells you how many crashes were reported. Without knowing how much people drove, walked or cycled, it cannot tell you how likely a crash was on a trip.
Location identifiers and severity codes
These are source-system labels used to match places and classify recorded outcomes. They are not independent proof of a city boundary or the cause of a crash.
Back to top ↑

Public records. A clearer local picture.

Explore the patterns in another Texas community.

Explore another city →