CrashDNA

Crash data.
Real-world context.

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

Bryan Crash Guide.

Brazos County

Reported crash counts, locations and trends in Bryan.

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,551 2.0% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes5 1 more5 vs. 4
Compared with Oct 1, 2024 to Sep 30, 2025
People killed5 No change5 vs. 5
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured39 13.3% fewerCompared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 2.0%.

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 Bryan

Bryan is a city in Brazos 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

Bryan’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 1,551 reported crashes in Bryan. That is 31 fewer than the 1,582 recorded for the corresponding dates a year earlier—a 2.0% decrease in reported crashes.

North Earl Rudder Freeway appears repeatedly in the reports, with 149 crashes listed under that road name. The 5 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 148 of the 1,551 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 Bryan’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,551 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
04895143190JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 141 reported crashesFeb 2022: 153 reported crashesMar 2022: 169 reported crashesApr 2022: 133 reported crashesMay 2022: 162 reported crashesJun 2022: 114 reported crashesJul 2022: 129 reported crashesAug 2022: 161 reported crashesSep 2022: 174 reported crashesOct 2022: 163 reported crashesNov 2022: 190 reported crashesDec 2022: 160 reported crashesJan 2023: 142 reported crashesFeb 2023: 147 reported crashesMar 2023: 178 reported crashesApr 2023: 160 reported crashesMay 2023: 155 reported crashesJun 2023: 136 reported crashesJul 2023: 146 reported crashesAug 2023: 176 reported crashesSep 2023: 165 reported crashesOct 2023: 188 reported crashesNov 2023: 138 reported crashesDec 2023: 121 reported crashesJan 2024: 148 reported crashesFeb 2024: 129 reported crashesMar 2024: 147 reported crashesApr 2024: 165 reported crashesMay 2024: 138 reported crashesJun 2024: 122 reported crashesJul 2024: 110 reported crashesAug 2024: 128 reported crashesSep 2024: 150 reported crashesOct 2024: 158 reported crashesNov 2024: 147 reported crashesDec 2024: 139 reported crashesJan 2025: 132 reported crashesFeb 2025: 127 reported crashesMar 2025: 116 reported crashesApr 2025: 124 reported crashesMay 2025: 131 reported crashesJun 2025: 100 reported crashesJul 2025: 102 reported crashesAug 2025: 146 reported crashesSep 2025: 160 reported crashesOct 2025: 150 reported crashesNov 2025: 153 reported crashesDec 2025: 145 reported crashesJan 2026: 118 reported crashesFeb 2026: 125 reported crashesMar 2026: 145 reported crashesApr 2026: 120 reported crashesMay 2026: 118 reported crashesJun 2026: 97 reported crashesJul 2026: 118 reported crashesAug 2026: 125 reported crashesSep 2026: 137 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan141142148132118
Feb153147129127125
Mar169178147116145
Apr133160165124120
May162155138131118
Jun11413612210097
Jul129146110102118
Aug161176128146125
Sep174165150160137
Oct163188158150—
Nov190138147153—
Dec160121139145—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Bryan recorded 1,103 crashes, compared with 1,138 over the matching dates a year earlier. That is 3.1% 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

07414812 AM: 16 reported crashes12 AM1 AM: 17 reported crashes2 AM: 20 reported crashes3 AM: 12 reported crashes3 AM4 AM: 11 reported crashes5 AM: 19 reported crashes6 AM: 42 reported crashes6 AM7 AM: 86 reported crashes8 AM: 85 reported crashes9 AM: 71 reported crashes9 AM10 AM: 53 reported crashes11 AM: 84 reported crashes12 PM: 106 reported crashes12 PM1 PM: 97 reported crashes2 PM: 107 reported crashes3 PM: 120 reported crashes3 PM4 PM: 128 reported crashes5 PM: 148 reported crashes6 PM: 93 reported crashes6 PM7 PM: 72 reported crashes8 PM: 62 reported crashes9 PM: 48 reported crashes9 PM10 PM: 30 reported crashes11 PM: 24 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM16000
1 AM17001
2 AM20000
3 AM12000
4 AM11002
5 AM19000
6 AM42001
7 AM86000
8 AM85001
9 AM71000
10 AM53001
11 AM84003
12 PM106004
1 PM97001
2 PM107113
3 PM120002
4 PM128113
5 PM148002
6 PM93117
7 PM72003
8 PM62111
9 PM48112
10 PM30001
11 PM24001

Day of the week

0131261Sun: 164 reported crashesSun164Mon: 214 reported crashesMon214Tue: 216 reported crashesTue216Wed: 246 reported crashesWed246Thu: 261 reported crashesThu261Fri: 257 reported crashesFri257Sat: 193 reported crashesSat193
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun164114
Mon214003
Tue216118
Wed246006
Thu261229
Fri257006
Sat193113

Month by month

0771532025-10: 150 reported crashes10/252025-11: 153 reported crashes2025-12: 145 reported crashes12/252026-01: 118 reported crashes2026-02: 125 reported crashes02/262026-03: 145 reported crashes2026-04: 120 reported crashes04/262026-05: 118 reported crashes2026-06: 97 reported crashes06/262026-07: 118 reported crashes2026-08: 125 reported crashes08/262026-09: 137 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10150116
2025-11153006
2025-12145003
2026-01118004
2026-02125112
2026-03145004
2026-04120111
2026-05118110
2026-0697002
2026-07118005
2026-08125004
2026-09137112

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved109
  • Commercial vehicle involved101
  • Motorcycle involved38
  • Pedestrian involved12
  • Bicycle involved11

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 involved109224
Commercial vehicle involved101223
Motorcycle involved381110
Pedestrian involved12000
Bicycle involved11001
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. North Earl Rudder Freeway149 crashes
  2. South Texas Avenue106 crashes
  3. Briarcrest Drive103 crashes
  4. North Harvey Mitchell Parkway85 crashes
  5. East Villa Maria Road74 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
N EARL RUDDER FWY149225
S TEXAS AVE106000
BRIARCREST DR103000
N HARVEY MITCHELL PKWY85006
E VILLA MARIA RD74000
W VILLA MARIA RD68002
N TEXAS AVE59001
BOONVILLE RD54001
E WILLIAM JOEL BRYAN PKWY52000
E 29TH ST46001
SAN JACINTO LN38000
WELLBORN RD30000
S COLLEGE AVE24000
JOHN SHARP PKWY20110
E NOT REPORTED15000
W 28TH ST15000
TABOR RD13001
FINFEATHER RD12002
AUSTINS COLONY PKWY11000
BECK ST11000
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
BRIARCREST DR & N EARL RUDDER FWY19000
AUSTINS COLONY PKWY & BOONVILLE RD7000
BRIARCREST DR & E 29TH ST7000
BRIARCREST DR & OAK RIDGE DR7000
JOHN SHARP PKWY & LEONARD RD7000
E WILLIAM JOEL BRYAN PKWY & JUNE ST6000
E WILLIAM JOEL BRYAN PKWY & N COULTER DR6000
N ROSEMARY DR & S TEXAS AVE6000
N SIMS AVE & SAN JACINTO LN6000
W VILLA MARIA RD & WILLIS VANHOOK DR6000
BECK ST & PALASOTA DR5000
E 23RD ST & N TEXAS AVE5000
E VILLA MARIA RD & S TEXAS AVE5000
E VILLA MARIA RD & WAYSIDE DR5000
JONES RD & W VILLA MARIA RD5001
BARAK LN & E 29TH ST4000
BRIARCREST DR & BROADMOOR DR4000
CARTER CREEK PKWY & E VILLA MARIA RD4000
CAVITT AVE & E VILLA MARIA RD4000
E 29TH ST & S TEXAS AVE4000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Bryan Crash Guide. Bryan — Brazos 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/bryan/

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

Bryan city · Brazos County. Reported city code 55; county codes 21. Current Census place identifier 4810912 (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 BRYAN, 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, 63 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; 13 lack a usable road label. 1,042 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:06:02.852Z. 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 →