CrashDNA

Crash data.
Real-world context.

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

Temple Crash Guide.

Bell County

Reported crash counts, locations and trends in Temple.

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 crashes2,136 1.5% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes19 8 more19 vs. 11
Compared with Oct 1, 2024 to Sep 30, 2025
People killed19 7 more19 vs. 12
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured64 39.1% moreCompared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 1.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 Temple

Temple is a city in Bell 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

Temple’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 2,136 reported crashes in Temple. That is 33 fewer than the 2,169 recorded for the corresponding dates a year earlier—a 1.5% decrease in reported crashes.

West Adams Avenue appears repeatedly in the reports, with 211 crashes listed under that road name. The 5 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 189 of the 2,136 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 Temple’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 (2,136 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
056112168224JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 124 reported crashesFeb 2022: 123 reported crashesMar 2022: 131 reported crashesApr 2022: 144 reported crashesMay 2022: 128 reported crashesJun 2022: 133 reported crashesJul 2022: 143 reported crashesAug 2022: 145 reported crashesSep 2022: 137 reported crashesOct 2022: 173 reported crashesNov 2022: 147 reported crashesDec 2022: 173 reported crashesJan 2023: 141 reported crashesFeb 2023: 144 reported crashesMar 2023: 138 reported crashesApr 2023: 156 reported crashesMay 2023: 162 reported crashesJun 2023: 133 reported crashesJul 2023: 135 reported crashesAug 2023: 164 reported crashesSep 2023: 159 reported crashesOct 2023: 164 reported crashesNov 2023: 174 reported crashesDec 2023: 155 reported crashesJan 2024: 138 reported crashesFeb 2024: 151 reported crashesMar 2024: 158 reported crashesApr 2024: 166 reported crashesMay 2024: 170 reported crashesJun 2024: 168 reported crashesJul 2024: 170 reported crashesAug 2024: 204 reported crashesSep 2024: 187 reported crashesOct 2024: 224 reported crashesNov 2024: 187 reported crashesDec 2024: 185 reported crashesJan 2025: 135 reported crashesFeb 2025: 146 reported crashesMar 2025: 189 reported crashesApr 2025: 181 reported crashesMay 2025: 177 reported crashesJun 2025: 183 reported crashesJul 2025: 193 reported crashesAug 2025: 178 reported crashesSep 2025: 191 reported crashesOct 2025: 198 reported crashesNov 2025: 201 reported crashesDec 2025: 196 reported crashesJan 2026: 146 reported crashesFeb 2026: 126 reported crashesMar 2026: 167 reported crashesApr 2026: 176 reported crashesMay 2026: 198 reported crashesJun 2026: 191 reported crashesJul 2026: 186 reported crashesAug 2026: 176 reported crashesSep 2026: 175 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan124141138135146
Feb123144151146126
Mar131138158189167
Apr144156166181176
May128162170177198
Jun133133168183191
Jul143135170193186
Aug145164204178176
Sep137159187191175
Oct173164224198—
Nov147174187201—
Dec173155185196—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Temple recorded 1,541 crashes, compared with 1,573 over the matching dates a year earlier. That is 2.0% 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

09518912 AM: 24 reported crashes12 AM1 AM: 13 reported crashes2 AM: 29 reported crashes3 AM: 20 reported crashes3 AM4 AM: 18 reported crashes5 AM: 35 reported crashes6 AM: 50 reported crashes6 AM7 AM: 115 reported crashes8 AM: 104 reported crashes9 AM: 88 reported crashes9 AM10 AM: 110 reported crashes11 AM: 119 reported crashes12 PM: 144 reported crashes12 PM1 PM: 142 reported crashes2 PM: 133 reported crashes3 PM: 174 reported crashes3 PM4 PM: 180 reported crashes5 PM: 189 reported crashes6 PM: 132 reported crashes6 PM7 PM: 103 reported crashes8 PM: 79 reported crashes9 PM: 64 reported crashes9 PM10 PM: 42 reported crashes11 PM: 29 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM24334
1 AM13000
2 AM29114
3 AM20112
4 AM18112
5 AM35111
6 AM50002
7 AM115113
8 AM104001
9 AM88002
10 AM110003
11 AM119003
12 PM144111
1 PM142006
2 PM133332
3 PM174225
4 PM180114
5 PM189001
6 PM132112
7 PM103114
8 PM79115
9 PM64115
10 PM42000
11 PM29002

Day of the week

0180360Sun: 188 reported crashesSun188Mon: 336 reported crashesMon336Tue: 328 reported crashesTue328Wed: 338 reported crashesWed338Thu: 331 reported crashesThu331Fri: 360 reported crashesFri360Sat: 255 reported crashesSat255
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun188225
Mon3364411
Tue328449
Wed338224
Thu331336
Fri3602212
Sat2552217

Month by month

01012012025-10: 198 reported crashes10/252025-11: 201 reported crashes2025-12: 196 reported crashes12/252026-01: 146 reported crashes2026-02: 126 reported crashes02/262026-03: 167 reported crashes2026-04: 176 reported crashes04/262026-05: 198 reported crashes2026-06: 191 reported crashes06/262026-07: 186 reported crashes2026-08: 176 reported crashes08/262026-09: 175 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10198226
2025-11201119
2025-12196114
2026-01146333
2026-02126442
2026-03167229
2026-04176003
2026-05198007
2026-06191227
2026-07186335
2026-08176116
2026-09175003

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved212
  • Commercial vehicle involved168
  • Motorcycle involved50
  • Pedestrian involved41
  • Bicycle involved27

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 involved212224
Commercial vehicle involved168224
Motorcycle involved503314
Pedestrian involved41334
Bicycle involved27115
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. West Adams Avenue211 crashes
  2. South 31st Street172 crashes
  3. South General Bruce Drive152 crashes
  4. Southwest H K Dodgen Loop84 crashes
  5. Southwest Hk Dodgen Loop70 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 ADAMS AVE211114
S 31ST ST172003
S GENERAL BRUCE DR152114
SW H K DODGEN LOOP84000
SW HK DODGEN LOOP70001
N GENERAL BRUCE DR68112
IH 3557000
AIRPORT RD53113
S 5TH ST46001
S 1ST ST38002
W CENTRAL AVE36001
S IH 3534221
NW HK DODGEN LOOP31002
E ADAMS AVE25002
OLD WACO RD22000
SH 31722001
SE HK DODGEN LOOP21002
N 3RD ST19000
NE HK DODGEN LOOP19110
MARLANDWOOD RD17000
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
S GENERAL BRUCE DR & SW H K DODGEN LOOP34000
S GENERAL BRUCE DR & SW HK DODGEN LOOP25000
S 31ST ST & SW H K DODGEN LOOP18001
N GENERAL BRUCE DR & W ADAMS AVE15000
S 1ST ST & W H AVE12000
S 31ST ST & SW HK DODGEN LOOP11000
AZALEA DR & S 31ST ST9001
N 3RD ST & W CENTRAL AVE9000
NW HK DODGEN LOOP & WENDLAND RD9001
N 31ST ST & W ADAMS AVE8000
OLD WACO RD & W ADAMS AVE8000
S 1ST ST & W G AVE7000
E ADAMS AVE & N 16TH ST6000
N 23RD ST & W ADAMS AVE6000
NW H K DODGEN LOOP & WENDLAND RD6000
AZALEA DR & LOWES DR5000
E ADAMS AVE & N MAIN ST5000
MEADOWBROOK DR & W ADAMS AVE5000
N 29TH ST & W CENTRAL AVE5000
OLD WACO RD & TARVER DR5000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Temple Crash Guide. Temple — Bell 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/temple/

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

Temple city · Bell County. Reported city code 424; county codes 14. Current Census place identifier 4872176 (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 TEMPLE, 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, 322 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; 20 lack a usable road label. 1,233 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:33:45.116Z. 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 →