CrashDNA

Crash data.
Real-world context.

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

San Marcos Crash Guide.

Guadalupe and Hays counties

Reported crash counts, locations and trends in San Marcos.

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 crashes1,608 0.5% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes6 4 fewer6 vs. 10
Compared with Oct 1, 2024 to Sep 30, 2025
People killed6 5 fewer6 vs. 11
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured65 3.2% moreCompared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 0.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 San Marcos

San Marcos is a city in Guadalupe and Hays 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

San Marcos’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 1,608 reported crashes in San Marcos. That is 8 more than the 1,600 recorded for the corresponding dates a year earlier—a 0.5% increase in reported crashes.

Interstate 35 appears repeatedly in the reports, with 159 crashes listed under that road name. The 5 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 132 of the 1,608 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 San Marcos’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 (1,608 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
04794141188JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 73 reported crashesFeb 2022: 87 reported crashesMar 2022: 118 reported crashesApr 2022: 103 reported crashesMay 2022: 91 reported crashesJun 2022: 132 reported crashesJul 2022: 93 reported crashesAug 2022: 114 reported crashesSep 2022: 137 reported crashesOct 2022: 156 reported crashesNov 2022: 109 reported crashesDec 2022: 118 reported crashesJan 2023: 90 reported crashesFeb 2023: 89 reported crashesMar 2023: 117 reported crashesApr 2023: 118 reported crashesMay 2023: 94 reported crashesJun 2023: 97 reported crashesJul 2023: 104 reported crashesAug 2023: 115 reported crashesSep 2023: 148 reported crashesOct 2023: 132 reported crashesNov 2023: 148 reported crashesDec 2023: 114 reported crashesJan 2024: 115 reported crashesFeb 2024: 114 reported crashesMar 2024: 107 reported crashesApr 2024: 133 reported crashesMay 2024: 115 reported crashesJun 2024: 139 reported crashesJul 2024: 96 reported crashesAug 2024: 127 reported crashesSep 2024: 154 reported crashesOct 2024: 144 reported crashesNov 2024: 141 reported crashesDec 2024: 123 reported crashesJan 2025: 118 reported crashesFeb 2025: 122 reported crashesMar 2025: 141 reported crashesApr 2025: 122 reported crashesMay 2025: 131 reported crashesJun 2025: 126 reported crashesJul 2025: 127 reported crashesAug 2025: 140 reported crashesSep 2025: 165 reported crashesOct 2025: 188 reported crashesNov 2025: 159 reported crashesDec 2025: 146 reported crashesJan 2026: 111 reported crashesFeb 2026: 115 reported crashesMar 2026: 126 reported crashesApr 2026: 139 reported crashesMay 2026: 121 reported crashesJun 2026: 115 reported crashesJul 2026: 106 reported crashesAug 2026: 144 reported crashesSep 2026: 138 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan7390115118111
Feb8789114122115
Mar118117107141126
Apr103118133122139
May9194115131121
Jun13297139126115
Jul9310496127106
Aug114115127140144
Sep137148154165138
Oct156132144188—
Nov109148141159—
Dec118114123146—
Same-period year-to-date comparison

From January 1 through 2026-09-30, San Marcos recorded 1,115 crashes, compared with 1,192 over the matching dates a year earlier. That is 6.5% fewer reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 5 PM.

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

Time of day

06613212 AM: 28 reported crashes12 AM1 AM: 41 reported crashes2 AM: 53 reported crashes3 AM: 24 reported crashes3 AM4 AM: 22 reported crashes5 AM: 19 reported crashes6 AM: 26 reported crashes6 AM7 AM: 52 reported crashes8 AM: 52 reported crashes9 AM: 56 reported crashes9 AM10 AM: 60 reported crashes11 AM: 74 reported crashes12 PM: 96 reported crashes12 PM1 PM: 97 reported crashes2 PM: 103 reported crashes3 PM: 113 reported crashes3 PM4 PM: 122 reported crashes5 PM: 132 reported crashes6 PM: 131 reported crashes6 PM7 PM: 91 reported crashes8 PM: 65 reported crashes9 PM: 51 reported crashes9 PM10 PM: 52 reported crashes11 PM: 48 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM28000
1 AM41001
2 AM53002
3 AM24001
4 AM22000
5 AM19002
6 AM26112
7 AM52003
8 AM52006
9 AM56001
10 AM60004
11 AM74001
12 PM96002
1 PM97008
2 PM103000
3 PM113002
4 PM122003
5 PM132004
6 PM131115
7 PM91117
8 PM65116
9 PM51002
10 PM52221
11 PM48002

Day of the week

0133266Sun: 197 reported crashesSun197Mon: 228 reported crashesMon228Tue: 211 reported crashesTue211Wed: 239 reported crashesWed239Thu: 237 reported crashesThu237Fri: 266 reported crashesFri266Sat: 230 reported crashesSat230
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun197226
Mon2281113
Tue2110010
Wed239008
Thu2370010
Fri2661111
Sat230227

Month by month

0941882025-10: 188 reported crashes10/252025-11: 159 reported crashes2025-12: 146 reported crashes12/252026-01: 111 reported crashes2026-02: 115 reported crashes02/262026-03: 126 reported crashes2026-04: 139 reported crashes04/262026-05: 121 reported crashes2026-06: 115 reported crashes06/262026-07: 106 reported crashes2026-08: 144 reported crashes08/262026-09: 138 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10188119
2025-11159004
2025-12146114
2026-011110010
2026-02115113
2026-03126117
2026-04139004
2026-05121001
2026-06115005
2026-07106005
2026-08144115
2026-09138118

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved146
  • Commercial vehicle involved120
  • Pedestrian involved33
  • Motorcycle involved31
  • Bicycle involved15

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 involved146116
Commercial vehicle involved120116
Pedestrian involved33228
Motorcycle involved311111
Bicycle involved15003
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. Interstate 35159 crashes
  2. South Interstate 35143 crashes
  3. North Interstate 35140 crashes
  4. Aquarena Springs Drive79 crashes
  5. State Highway 12354 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 35159002
S IH 35143113
N IH 35140118
AQUARENA SPRINGS DR79003
SH 12354006
SH 8044115
WONDER WORLD DR43110
E HOPKINS ST38000
SL 8236001
RM 1232000
SH 2128000
W HOPKINS ST28000
THORPE LN26001
HUNTER RD25111
HWY 8023002
MOORE ST21001
N IH 35 HWY21000
RIVER RD20000
S GUADALUPE ST20001
UNIVERSITY DR17003
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
AQUARENA SPRINGS DR & THORPE LN13000
S IH 35 & WONDER WORLD DR8000
E MLK DR & S LBJ DR7000
FM 2439 & RM 127000
N EDWARD GARY ST & UNIVERSITY DR7001
AQUARENA SPRINGS DR & N IH 355000
E MCCARTY LN & HUNTER RD5001
HARRIS HILL RD & SH 215000
MOORE ST & W HUTCHISON ST5000
RIVER RD & SH 805003
RM 12 & S IH 355000
AQUARENA SPRINGS DR & CHARLES AUSTIN DR4000
AQUARENA SPRINGS DR & WEST AVE4000
BURLESON ST & MOORE ST4000
CHEATHAM ST & S GUADALUPE ST4000
E HOPKINS ST & N LBJ DR4000
E HUTCHISON ST & N LBJ DR4000
E MCCARTY LN & S IH 354000
HUNTER RD & WONDER WORLD DR4000
N COMANCHE ST & W HOPKINS ST4000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. San Marcos Crash Guide. San Marcos — Guadalupe County and Hays 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/san-marcos/

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

San Marcos city · Guadalupe County and Hays County. Reported city code 383; county codes 94, 105. Current Census place identifier 4865600 (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 SAN MARCOS, 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, 165 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. 1,092 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:31:03.099Z. 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 →