Whitesboro Crash Guide.
Grayson County
Reported crash counts, locations and trends in Whitesboro.
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 13.5%.
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 Whitesboro
Whitesboro is a city in Grayson 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.
Whitesboro’s crash picture
From Oct 1, 2025 through Sep 30, 2026, the available records include 59 reported crashes in Whitesboro. That is 7 more than the 52 recorded for the corresponding dates a year earlier—a 13.5% increase in reported crashes.
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 Whitesboro’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 (59 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 13.5%.
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 | 58 | 1 | 1 | 5 |
| 2023 | 61 | 0 | 0 | 4 |
| 2024 | 55 | 1 | 2 | 6 |
| 2025 | 61 | 1 | 1 | 2 |
| 2026 (partial) | 38 | 0 | 0 | 2 |
* 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 | 5 | 4 | 3 | 1 | 1 |
| Feb | 6 | 3 | 5 | 4 | 9 |
| Mar | 7 | 6 | 3 | 8 | 4 |
| Apr | 3 | 4 | 6 | 4 | 5 |
| May | 4 | 7 | 2 | 10 | 7 |
| Jun | 4 | 5 | 4 | 2 | 2 |
| Jul | 3 | 3 | 4 | 3 | 1 |
| Aug | 5 | 4 | 10 | 4 | 5 |
| Sep | 3 | 6 | 6 | 4 | 4 |
| Oct | 7 | 6 | 3 | 6 | — |
| Nov | 6 | 6 | 3 | 4 | — |
| Dec | 5 | 7 | 6 | 11 | — |
Same-period year-to-date comparison
From January 1 through 2026-09-30, Whitesboro recorded 38 crashes, compared with 40 over the matching dates a year earlier. That is 5.0% fewer reported crashes.
When crashes are reported.
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 | 0 | 0 | 0 | 0 |
| 1 AM | 0 | 0 | 0 | 0 |
| 2 AM | 0 | 0 | 0 | 0 |
| 3 AM | 0 | 0 | 0 | 0 |
| 4 AM | 0 | 0 | 0 | 0 |
| 5 AM | 0 | 0 | 0 | 0 |
| 6 AM | 4 | 0 | 0 | 1 |
| 7 AM | 4 | 0 | 0 | 0 |
| 8 AM | 3 | 0 | 0 | 0 |
| 9 AM | 2 | 0 | 0 | 0 |
| 10 AM | 1 | 0 | 0 | 0 |
| 11 AM | 4 | 0 | 0 | 0 |
| 12 PM | 4 | 0 | 0 | 0 |
| 1 PM | 6 | 0 | 0 | 1 |
| 2 PM | 4 | 0 | 0 | 1 |
| 3 PM | 1 | 0 | 0 | 0 |
| 4 PM | 4 | 0 | 0 | 1 |
| 5 PM | 5 | 0 | 0 | 0 |
| 6 PM | 7 | 1 | 1 | 0 |
| 7 PM | 2 | 0 | 0 | 0 |
| 8 PM | 1 | 0 | 0 | 0 |
| 9 PM | 3 | 0 | 0 | 0 |
| 10 PM | 2 | 0 | 0 | 0 |
| 11 PM | 2 | 0 | 0 | 0 |
Day of the week
View the data table
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| Sun | 1 | 0 | 0 | 0 |
| Mon | 6 | 0 | 0 | 1 |
| Tue | 12 | 0 | 0 | 0 |
| Wed | 8 | 0 | 0 | 0 |
| Thu | 12 | 0 | 0 | 0 |
| Fri | 11 | 0 | 0 | 1 |
| Sat | 9 | 1 | 1 | 2 |
Month by month
View the data table
| Group | Crashes | Fatal crashes | People killed | People seriously injured |
|---|---|---|---|---|
| 2025-10 | 6 | 1 | 1 | 0 |
| 2025-11 | 4 | 0 | 0 | 1 |
| 2025-12 | 11 | 0 | 0 | 1 |
| 2026-01 | 1 | 0 | 0 | 0 |
| 2026-02 | 9 | 0 | 0 | 0 |
| 2026-03 | 4 | 0 | 0 | 0 |
| 2026-04 | 5 | 0 | 0 | 0 |
| 2026-05 | 7 | 0 | 0 | 1 |
| 2026-06 | 2 | 0 | 0 | 0 |
| 2026-07 | 1 | 0 | 0 | 0 |
| 2026-08 | 5 | 0 | 0 | 0 |
| 2026-09 | 4 | 0 | 0 | 1 |
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 |
|---|---|---|---|---|
| Truck / truck-tractor involved | 5 | 0 | 0 | 0 |
| Motorcycle involved | 2 | 1 | 1 | 1 |
| Commercial vehicle involved | 1 | 0 | 0 | 0 |
| Bicycle involved | 1 | 0 | 0 | 0 |
| Pedestrian involved | 0 | 0 | 0 | 0 |
Roads with the most reports.
- US 3777 crashes
- North Union Street4 crashes
- US Highway 3773 crashes
- Business Highway 3772 crashes
- East Main Street2 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 |
|---|---|---|---|---|
| US 377 | 7 | 0 | 0 | 0 |
| N UNION ST | 4 | 0 | 0 | 0 |
| US HIGHWAY 377 | 3 | 0 | 0 | 0 |
| BUSINESS HIGHWAY 377 | 2 | 0 | 0 | 0 |
| E MAIN ST | 2 | 0 | 0 | 0 |
| E U S HIGHWAY 82 | 2 | 0 | 0 | 1 |
| HWY 377 | 2 | 0 | 0 | 0 |
| U S HIGHWAY 82 | 2 | 0 | 0 | 0 |
| US 377 HWY | 2 | 0 | 0 | 1 |
| US 82 | 2 | 0 | 0 | 1 |
| 4TH ST | 1 | 0 | 0 | 0 |
| ABNEY ST | 1 | 0 | 0 | 0 |
| BROADWAY ST | 1 | 1 | 1 | 0 |
| E HIGHWAY 82 | 1 | 0 | 0 | 1 |
| E US 82 | 1 | 0 | 0 | 0 |
| FORTH ST | 1 | 0 | 0 | 0 |
| FOURTH ST | 1 | 0 | 0 | 0 |
| HIGHWAY 377 | 1 | 0 | 0 | 0 |
| HIGHWAY 82 | 1 | 0 | 0 | 0 |
| JOLINDA LN | 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 |
|---|---|---|---|---|
| ANDERSON RD & US HIGHWAY 377 | 2 | 0 | 0 | 0 |
| BU 377 B & US 377 | 2 | 0 | 0 | 0 |
| ANDERSON RD & US 377 | 1 | 0 | 0 | 0 |
| BEARCAT LN & WEST MAIN | 1 | 0 | 0 | 0 |
| BOIS D ARC ST & E HIGHWAY 82 | 1 | 0 | 0 | 1 |
| BROADWAY ST & PARKER LN | 1 | 1 | 1 | 0 |
| BU 377 B & US 377 HWY | 1 | 0 | 0 | 0 |
| BU 377 B HWY & US 377 HWY | 1 | 0 | 0 | 1 |
| BUSINESS US 377 B & HIGHWAY 377 | 1 | 0 | 0 | 0 |
| BUSINESS US HWY 377 HWY & US HIGHWAY 377 HWY | 1 | 0 | 0 | 0 |
| BYNUM ST & US 377 | 1 | 0 | 0 | 0 |
| E MAIN ST & WILSON ST | 1 | 0 | 0 | 0 |
| E U S HIGHWAY 82 & E U S HIGHWAY 82 | 1 | 0 | 0 | 1 |
| ELLA ST & HWY 377 | 1 | 0 | 0 | 0 |
| FORTH ST & WHITE ST | 1 | 0 | 0 | 0 |
| HALL ST & N UNION | 1 | 0 | 0 | 0 |
| MAIN ST & N UNION ST | 1 | 0 | 0 | 0 |
| N BUSINESS U S 377 & N U S HIGHWAY 377 | 1 | 0 | 0 | 0 |
| N BUSINESS US 377 B & N UNION | 1 | 0 | 0 | 0 |
| N UNION ST & OTIS ST | 1 | 0 | 0 | 0 |
Cite this guide.
Using these figures? Keep the reporting period and source with them.
CrashDNA. Whitesboro Crash Guide. Whitesboro — Grayson 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/whitesboro/
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
Whitesboro city · Grayson County. Reported city code 458; county codes 91. Current Census place identifier 4878532 (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 WHITESBORO, 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, 4 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. 34 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:36:35.085Z. 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.