Breckenridge Crash Guide.
Stephens County
Reported crash counts, locations and trends in Breckenridge.
Guide figures: Oct 1, 2025 to Sep 30, 2026. Based on records available through Sep 30, 2026. The map uses a separate calendar year.
Compared with Oct 1, 2024 to Sep 30, 2025
Compared with Oct 1, 2024 to Sep 30, 2025
Compared with Oct 1, 2024 to Sep 30, 2025
Reported crashes rose 54.1%.
Compared with Oct 1, 2024 to Sep 30, 2025. Counts alone do not tell us how risky a trip is.
Explore the data →Getting around Breckenridge
Breckenridge is a city in Stephens 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.
Breckenridge’s crash picture
From Oct 1, 2025 through Sep 30, 2026, the available records include 114 reported crashes in Breckenridge. That is 40 more than the 74 recorded for the corresponding dates a year earlier—a 54.1% increase in reported crashes.
West Walker Street appears repeatedly in the reports, with 39 crashes listed under that road name. The 4 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 24 of the 114 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 →
Explore Breckenridge’s reported crash locations.
Named areas with the most matching crashes. Choose an area to zoom in.
- The ranked areas appear when the map loads.
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 (114 crashes). The count below follows the selected map year and filters.
Scroll the page normally. Enable map movement to pan or pinch the map; disable it to keep reading.
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.
| Reported road / area | Crashes | Fatal crashes | People killed | People seriously injured |
|---|
Reported crashes rose 54.1%.
Compared with Oct 1, 2024 to Sep 30, 2025. Counts alone do not tell us how risky a trip is.
Reported crashes by year
View the data table
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| 2022 | 105 | 0 | 0 | 1 |
| 2023 | 78 | 0 | 0 | 1 |
| 2024 | 84 | 1 | 1 | 6 |
| 2025 | 96 | 0 | 0 | 2 |
| 2026 (partial) | 79 | 0 | 0 | 5 |
* Partial year. Full and partial years are not directly comparable.
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.
View year-over-year monthly data
| Month | 2022 | 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|---|---|
| Jan | 6 | 6 | 6 | 9 | 4 |
| Feb | 10 | 7 | 8 | 8 | 7 |
| Mar | 11 | 10 | 5 | 10 | 20 |
| Apr | 7 | 3 | 4 | 5 | 5 |
| May | 10 | 4 | 13 | 6 | 6 |
| Jun | 10 | 7 | 4 | 7 | 12 |
| Jul | 11 | 3 | 6 | 9 | 9 |
| Aug | 8 | 4 | 16 | 4 | 6 |
| Sep | 9 | 7 | 9 | 3 | 10 |
| Oct | 7 | 11 | 4 | 13 | — |
| Nov | 5 | 9 | 6 | 7 | — |
| Dec | 11 | 7 | 3 | 15 | — |
Same-period year-to-date comparison
From January 1 through 2026-09-30, Breckenridge recorded 79 crashes, compared with 61 over the matching dates a year earlier. That is 29.5% more reported crashes.
Reported crashes peak at 4 PM.
Oct 1, 2025 to Sep 30, 2026 · Known hours only.
Time of day
View the data table
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| 12 AM | 2 | 0 | 0 | 1 |
| 1 AM | 0 | 0 | 0 | 0 |
| 2 AM | 0 | 0 | 0 | 0 |
| 3 AM | 0 | 0 | 0 | 0 |
| 4 AM | 1 | 0 | 0 | 0 |
| 5 AM | 1 | 0 | 0 | 0 |
| 6 AM | 2 | 0 | 0 | 0 |
| 7 AM | 4 | 0 | 0 | 0 |
| 8 AM | 6 | 0 | 0 | 0 |
| 9 AM | 2 | 0 | 0 | 0 |
| 10 AM | 4 | 0 | 0 | 0 |
| 11 AM | 8 | 0 | 0 | 0 |
| 12 PM | 9 | 0 | 0 | 1 |
| 1 PM | 7 | 0 | 0 | 0 |
| 2 PM | 5 | 0 | 0 | 0 |
| 3 PM | 9 | 0 | 0 | 0 |
| 4 PM | 24 | 0 | 0 | 1 |
| 5 PM | 6 | 0 | 0 | 0 |
| 6 PM | 8 | 0 | 0 | 2 |
| 7 PM | 5 | 0 | 0 | 1 |
| 8 PM | 4 | 0 | 0 | 1 |
| 9 PM | 2 | 0 | 0 | 0 |
| 10 PM | 4 | 0 | 0 | 0 |
| 11 PM | 1 | 0 | 0 | 0 |
Day of the week
View the data table
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| Sun | 13 | 0 | 0 | 0 |
| Mon | 20 | 0 | 0 | 0 |
| Tue | 7 | 0 | 0 | 3 |
| Wed | 20 | 0 | 0 | 1 |
| Thu | 18 | 0 | 0 | 1 |
| Fri | 24 | 0 | 0 | 1 |
| Sat | 12 | 0 | 0 | 1 |
Month by month
View the data table
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| 2025-10 | 13 | 0 | 0 | 1 |
| 2025-11 | 7 | 0 | 0 | 1 |
| 2025-12 | 15 | 0 | 0 | 0 |
| 2026-01 | 4 | 0 | 0 | 0 |
| 2026-02 | 7 | 0 | 0 | 0 |
| 2026-03 | 20 | 0 | 0 | 2 |
| 2026-04 | 5 | 0 | 0 | 0 |
| 2026-05 | 6 | 0 | 0 | 1 |
| 2026-06 | 12 | 0 | 0 | 2 |
| 2026-07 | 9 | 0 | 0 | 0 |
| 2026-08 | 6 | 0 | 0 | 0 |
| 2026-09 | 10 | 0 | 0 | 0 |
Selected period; * partial month. Outlined bars mean missing coverage, not zero crashes.
Crashes by road-user involvement.
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.
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| Commercial vehicle involved | 13 | 0 | 0 | 0 |
| Truck / truck-tractor involved | 13 | 0 | 0 | 0 |
| Motorcycle involved | 3 | 0 | 0 | 2 |
| Pedestrian involved | 1 | 0 | 0 | 0 |
| Bicycle involved | 0 | 0 | 0 | 0 |
Roads with the most reports.
- West Walker Street39 crashes
- East Walker Street12 crashes
- West Walker4 crashes
- North Farm-to-Market Road 30993 crashes
- North Graham Street3 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
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| W WALKER ST | 39 | 0 | 0 | 1 |
| E WALKER ST | 12 | 0 | 0 | 0 |
| W WALKER | 4 | 0 | 0 | 2 |
| N FM 3099 | 3 | 0 | 0 | 0 |
| N GRAHAM ST | 3 | 0 | 0 | 0 |
| N PARKS ST | 3 | 0 | 0 | 0 |
| N ROSE ST | 3 | 0 | 0 | 0 |
| W HULLUM ST | 3 | 0 | 0 | 0 |
| US 180 | 2 | 0 | 0 | 0 |
| W ELM ST | 2 | 0 | 0 | 1 |
| W LINDSEY ST | 2 | 0 | 0 | 0 |
| W WILLIAMS ST | 2 | 0 | 0 | 1 |
| E CONNELL ST | 1 | 0 | 0 | 0 |
| E DYER ST | 1 | 0 | 0 | 0 |
| E ELLIOTT ST | 1 | 0 | 0 | 1 |
| E HULLUM ST | 1 | 0 | 0 | 0 |
| FM 287 | 1 | 0 | 0 | 0 |
| FM 3099 | 1 | 0 | 0 | 0 |
| INDUSTRIAL LOOP PKWY | 1 | 0 | 0 | 1 |
| N 3099 | 1 | 0 | 0 | 0 |
Reported intersection pairs
Only records flagged as intersections with both street names. These are reported labels—not verified geographic intersections.
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| N ROSE ST & W WALKER ST | 3 | 0 | 0 | 0 |
| S PECAN ST & W WALKER ST | 3 | 0 | 0 | 0 |
| E WALKER ST & N GRAHAM AVE | 2 | 0 | 0 | 0 |
| S HARDING ST & W WALKER ST | 2 | 0 | 0 | 0 |
| CACTUS CV & FM 3099 | 1 | 0 | 0 | 0 |
| CATCUS CV & N FM 3099 | 1 | 0 | 0 | 0 |
| CATUS COVE CV & N FM 3099 | 1 | 0 | 0 | 0 |
| E CONNELL ST & N FM 287 | 1 | 0 | 0 | 0 |
| E CONNELL ST & N GRAHAM ST | 1 | 0 | 0 | 0 |
| E DAVIS RD & N INDUSTRIAL BLVD BLVD | 1 | 0 | 0 | 0 |
| E DYER ST & N GRAHAM ST | 1 | 0 | 0 | 0 |
| E ELLIOTT ST & S GRAHAM ST | 1 | 0 | 0 | 1 |
| E HULLUM ST & S OLD CADDO AVE | 1 | 0 | 0 | 0 |
| E WALKER ST & N BAYLOR ST | 1 | 0 | 0 | 0 |
| E WALKER ST & N GRAHAM ST | 1 | 0 | 0 | 0 |
| E WALKER ST & S BRECKENRIDGE AVE | 1 | 0 | 0 | 0 |
| E WALKER ST & S BUTTE ST | 1 | 0 | 0 | 0 |
| E WALKER ST & S HARTFORD ST | 1 | 0 | 0 | 0 |
| E WILLIAMS ST & S FLINT ST | 1 | 0 | 0 | 0 |
| N COURT ST & W WALKER | 1 | 0 | 0 | 2 |
Cite this guide.
Using these figures? Keep the reporting period and source with them.
CrashDNA. Breckenridge Crash Guide. Breckenridge — Stephens 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/breckenridge/
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
Breckenridge city · Stephens County. Reported city code 47; county codes 215. Current Census place identifier 4810132 (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 BRECKENRIDGE, 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, 32 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; 0 lack a usable road label. 62 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:05:16.487Z. 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.
Public records. A clearer local picture.
Explore the patterns in another Texas community.