CrashDNA

Crash data.
Real-world context.

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

Elgin Crash Guide.

Bastrop and Travis counties

Reported crash counts, locations and trends in Elgin.

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 crashes310 4.4% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes2 No change2 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People killed3 No change3 vs. 3
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured2 7 fewer2 vs. 9
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 4.4%.

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 Elgin

Elgin is a city in Bastrop and Travis counties, 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

Elgin’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 310 reported crashes in Elgin. That is 13 more than the 297 recorded for the corresponding dates a year earlier—a 4.4% increase in reported crashes.

West US Highway 290 Highway appears repeatedly in the reports, with 48 crashes listed under that road name. The 6 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 33 of the 310 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 Elgin’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 (310 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
010192938JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 23 reported crashesFeb 2022: 19 reported crashesMar 2022: 21 reported crashesApr 2022: 24 reported crashesMay 2022: 28 reported crashesJun 2022: 19 reported crashesJul 2022: 21 reported crashesAug 2022: 25 reported crashesSep 2022: 23 reported crashesOct 2022: 34 reported crashesNov 2022: 24 reported crashesDec 2022: 25 reported crashesJan 2023: 26 reported crashesFeb 2023: 27 reported crashesMar 2023: 26 reported crashesApr 2023: 30 reported crashesMay 2023: 37 reported crashesJun 2023: 26 reported crashesJul 2023: 22 reported crashesAug 2023: 19 reported crashesSep 2023: 19 reported crashesOct 2023: 35 reported crashesNov 2023: 28 reported crashesDec 2023: 27 reported crashesJan 2024: 24 reported crashesFeb 2024: 28 reported crashesMar 2024: 24 reported crashesApr 2024: 33 reported crashesMay 2024: 27 reported crashesJun 2024: 23 reported crashesJul 2024: 22 reported crashesAug 2024: 30 reported crashesSep 2024: 20 reported crashesOct 2024: 29 reported crashesNov 2024: 25 reported crashesDec 2024: 25 reported crashesJan 2025: 20 reported crashesFeb 2025: 27 reported crashesMar 2025: 32 reported crashesApr 2025: 19 reported crashesMay 2025: 28 reported crashesJun 2025: 21 reported crashesJul 2025: 27 reported crashesAug 2025: 27 reported crashesSep 2025: 17 reported crashesOct 2025: 36 reported crashesNov 2025: 38 reported crashesDec 2025: 19 reported crashesJan 2026: 28 reported crashesFeb 2026: 18 reported crashesMar 2026: 38 reported crashesApr 2026: 21 reported crashesMay 2026: 30 reported crashesJun 2026: 26 reported crashesJul 2026: 12 reported crashesAug 2026: 22 reported crashesSep 2026: 22 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan2326242028
Feb1927282718
Mar2126243238
Apr2430331921
May2837272830
Jun1926232126
Jul2122222712
Aug2519302722
Sep2319201722
Oct34352936—
Nov24282538—
Dec25272519—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Elgin recorded 217 crashes, compared with 218 over the matching dates a year earlier. That is 0.5% fewer reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 6 PM.

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

Time of day

0173312 AM: 8 reported crashes12 AM1 AM: 3 reported crashes2 AM: 1 reported crash3 AM: 1 reported crash3 AM4 AM: 2 reported crashes5 AM: 8 reported crashes6 AM: 9 reported crashes6 AM7 AM: 13 reported crashes8 AM: 12 reported crashes9 AM: 14 reported crashes9 AM10 AM: 13 reported crashes11 AM: 18 reported crashes12 PM: 17 reported crashes12 PM1 PM: 17 reported crashes2 PM: 20 reported crashes3 PM: 27 reported crashes3 PM4 PM: 19 reported crashes5 PM: 29 reported crashes6 PM: 33 reported crashes6 PM7 PM: 16 reported crashes8 PM: 11 reported crashes9 PM: 10 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 AM8001
1 AM3000
2 AM1000
3 AM1000
4 AM2000
5 AM8000
6 AM9000
7 AM13000
8 AM12000
9 AM14000
10 AM13110
11 AM18000
12 PM17000
1 PM17000
2 PM20000
3 PM27000
4 PM19000
5 PM29000
6 PM33120
7 PM16000
8 PM11000
9 PM10001
10 PM6000
11 PM3000

Day of the week

03467Sun: 34 reported crashesSun34Mon: 47 reported crashesMon47Tue: 44 reported crashesTue44Wed: 36 reported crashesWed36Thu: 32 reported crashesThu32Fri: 67 reported crashesFri67Sat: 50 reported crashesSat50
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun34000
Mon47000
Tue44000
Wed36110
Thu32000
Fri67000
Sat50122

Month by month

019382025-10: 36 reported crashes10/252025-11: 38 reported crashes2025-12: 19 reported crashes12/252026-01: 28 reported crashes2026-02: 18 reported crashes02/262026-03: 38 reported crashes2026-04: 21 reported crashes04/262026-05: 30 reported crashes2026-06: 26 reported crashes06/262026-07: 12 reported crashes2026-08: 22 reported crashes08/262026-09: 22 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-1036122
2025-1138110
2025-1219000
2026-0128000
2026-0218000
2026-0338000
2026-0421000
2026-0530000
2026-0626000
2026-0712000
2026-0822000
2026-0922000

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved23
  • Commercial vehicle involved17
  • Motorcycle involved3
  • Pedestrian involved3
  • Bicycle involved1

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 involved23000
Commercial vehicle involved17000
Motorcycle involved3001
Pedestrian involved3000
Bicycle involved1000
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. West US Highway 290 Highway48 crashes
  2. East US Highway 290 Highway32 crashes
  3. West US Highway 29018 crashes
  4. East US Highway 29013 crashes
  5. North Main Street13 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
W US HWY 290 HWY48000
E US HWY 290 HWY32120
W US HWY 29018001
E US HWY 29013000
N MAIN ST13001
US HWY 29011000
S MAIN ST10000
COUNTY LINE RD8000
US HWY 290 HWY7000
FM 11006000
N AVENUE C AVE6000
LEE DILDY BLVD4000
LOOP 109 LOOP4000
N HWY 95 HWY4000
N SH 95 N HWY4000
US 2904000
E 2ND ST3000
E US 2903000
LEXINGTON RD3000
MARTIN LUTHUR KING BLVD3000
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
E US HWY 290 HWY & S HWY 95 HWY3120
E US HWY 290 HWY & S SH95 S HWY3000
LEE DILDY BLVD & W US HWY 290 HWY3000
RAMIREZ RD & W US HWY 290 HWY3000
ROY RIVERS RD & W US HWY 290 HWY3000
BASKET FLOWER BEND & E US HWY 2902000
E US HWY 290 HWY & WESTERN SKY BLVD2000
HARRIS ST & W US HWY 2902001
LEE DILDY BLVD & W US HWY 2902000
N MAIN ST & W 2ND ST2001
N SH 95 N HWY & W US HWY 290 HWY2000
SWENSON BLVD & W US HWY 2902000
W US HWY 290 HWY & W US HWY 290 HWY2000
109 LOOP & W 7TH ST1000
1100 & COUNTY LINE RD1000
2ND ST & LOOP 1091000
3RD ST & FM 11001000
95 FRONTAGE RD & SH 95 N1000
ADIRONDACK & SCHUYLERVILLE1000
BASKET FLOWER BEND & E US HWY 290 HWY1000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Elgin Crash Guide. Elgin — Bastrop County and Travis 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/elgin/

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

Elgin city · Bastrop County and Travis County. Reported city code 138; county codes 11, 227. Current Census place identifier 4823044 (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 ELGIN, 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, 17 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; 14 lack a usable road label. 163 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:11:39.881Z. 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 →