CrashDNA

Crash data.
Real-world context.

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

North Richland Hills Crash Guide.

Tarrant County

Reported crash counts, locations and trends in North Richland Hills.

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 crashes805 8.9% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes2 No change2 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People killed3 1 more3 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured12 1 fewer12 vs. 13
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 8.9%.

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 North Richland Hills

North Richland Hills is a city in Tarrant 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

North Richland Hills’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 805 reported crashes in North Richland Hills. That is 79 fewer than the 884 recorded for the corresponding dates a year earlier—a 8.9% decrease in reported crashes.

Rufe Snow Drive appears repeatedly in the reports, with 95 crashes listed under that road name. The 3 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 71 of the 805 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 North Richland Hills’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 (805 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
023456890JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 64 reported crashesFeb 2022: 60 reported crashesMar 2022: 62 reported crashesApr 2022: 55 reported crashesMay 2022: 71 reported crashesJun 2022: 66 reported crashesJul 2022: 80 reported crashesAug 2022: 64 reported crashesSep 2022: 70 reported crashesOct 2022: 66 reported crashesNov 2022: 90 reported crashesDec 2022: 60 reported crashesJan 2023: 65 reported crashesFeb 2023: 46 reported crashesMar 2023: 60 reported crashesApr 2023: 89 reported crashesMay 2023: 73 reported crashesJun 2023: 77 reported crashesJul 2023: 71 reported crashesAug 2023: 67 reported crashesSep 2023: 63 reported crashesOct 2023: 90 reported crashesNov 2023: 81 reported crashesDec 2023: 76 reported crashesJan 2024: 77 reported crashesFeb 2024: 65 reported crashesMar 2024: 84 reported crashesApr 2024: 72 reported crashesMay 2024: 65 reported crashesJun 2024: 74 reported crashesJul 2024: 85 reported crashesAug 2024: 82 reported crashesSep 2024: 64 reported crashesOct 2024: 90 reported crashesNov 2024: 77 reported crashesDec 2024: 85 reported crashesJan 2025: 58 reported crashesFeb 2025: 60 reported crashesMar 2025: 64 reported crashesApr 2025: 71 reported crashesMay 2025: 85 reported crashesJun 2025: 76 reported crashesJul 2025: 67 reported crashesAug 2025: 71 reported crashesSep 2025: 80 reported crashesOct 2025: 79 reported crashesNov 2025: 69 reported crashesDec 2025: 79 reported crashesJan 2026: 53 reported crashesFeb 2026: 65 reported crashesMar 2026: 72 reported crashesApr 2026: 57 reported crashesMay 2026: 63 reported crashesJun 2026: 72 reported crashesJul 2026: 62 reported crashesAug 2026: 70 reported crashesSep 2026: 64 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan6465775853
Feb6046656065
Mar6260846472
Apr5589727157
May7173658563
Jun6677747672
Jul8071856762
Aug6467827170
Sep7063648064
Oct66909079—
Nov90817769—
Dec60768579—
Same-period year-to-date comparison

From January 1 through 2026-09-30, North Richland Hills recorded 578 crashes, compared with 632 over the matching dates a year earlier. That is 8.5% fewer reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 3 PM.

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

Time of day

0367112 AM: 12 reported crashes12 AM1 AM: 13 reported crashes2 AM: 14 reported crashes3 AM: 8 reported crashes3 AM4 AM: 8 reported crashes5 AM: 24 reported crashes6 AM: 24 reported crashes6 AM7 AM: 44 reported crashes8 AM: 37 reported crashes9 AM: 34 reported crashes9 AM10 AM: 29 reported crashes11 AM: 36 reported crashes12 PM: 44 reported crashes12 PM1 PM: 42 reported crashes2 PM: 50 reported crashes3 PM: 71 reported crashes3 PM4 PM: 54 reported crashes5 PM: 52 reported crashes6 PM: 67 reported crashes6 PM7 PM: 45 reported crashes8 PM: 36 reported crashes9 PM: 26 reported crashes9 PM10 PM: 22 reported crashes11 PM: 13 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM12000
1 AM13000
2 AM14000
3 AM8000
4 AM8000
5 AM24001
6 AM24000
7 AM44001
8 AM37000
9 AM34000
10 AM29000
11 AM36110
12 PM44121
1 PM42000
2 PM50000
3 PM71002
4 PM54002
5 PM52001
6 PM67001
7 PM45002
8 PM36000
9 PM26000
10 PM22001
11 PM13000

Day of the week

065130Sun: 95 reported crashesSun95Mon: 109 reported crashesMon109Tue: 111 reported crashesTue111Wed: 125 reported crashesWed125Thu: 130 reported crashesThu130Fri: 128 reported crashesFri128Sat: 107 reported crashesSat107
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun95001
Mon109003
Tue111120
Wed125002
Thu130113
Fri128001
Sat107002

Month by month

040792025-10: 79 reported crashes10/252025-11: 69 reported crashes2025-12: 79 reported crashes12/252026-01: 53 reported crashes2026-02: 65 reported crashes02/262026-03: 72 reported crashes2026-04: 57 reported crashes04/262026-05: 63 reported crashes2026-06: 72 reported crashes06/262026-07: 62 reported crashes2026-08: 70 reported crashes08/262026-09: 64 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-1079003
2025-1169002
2025-1279002
2026-0153000
2026-0265001
2026-0372001
2026-0457000
2026-0563000
2026-0672231
2026-0762000
2026-0870002
2026-0964000

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved56
  • Commercial vehicle involved29
  • Motorcycle involved15
  • Pedestrian involved11
  • Bicycle involved7

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 involved56121
Commercial vehicle involved29122
Motorcycle involved15001
Pedestrian involved11004
Bicycle involved7000
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. Rufe Snow Drive95 crashes
  2. Northeast Loop 82094 crashes
  3. Davis Boulevard68 crashes
  4. Boulevard 2653 crashes
  5. Precinct Line Road32 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
RUFE SNOW DR95003
NE LOOP 82094122
DAVIS BLVD68113
BOULEVARD 2653001
PRECINCT LINE RD32000
MID CITIES BLVD30000
NE LOOP 820 EB28000
NE LOOP 820 WB26001
NE LOOP 820 WBA16000
BOULEVARD 26 BLVD13000
NE LOOP 820 EBA13000
GLENVIEW DR9000
HARWOOD RD8000
IH 820 EB7000
NE 820 LOOP7000
AIRPORT FWY6000
BEDFORD EULESS RD6000
BROWNING DR6000
NE LOOP 820 LOOP6000
NE NE LOOP 8206000
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
MID CITIES BLVD & PRECINCT LINE RD8000
DAVIS BLVD & HARWOOD RD5000
NE LOOP 820 & RUFE SNOW DR5000
NE LOOP 820 WBA & RUFE SNOW DR5002
BOULEVARD 26 & DAVIS BLVD4000
DICK LEWIS DR & RUFE SNOW DR4000
BEDFORD EULESS RD & BOULEVARD 263000
DAVIS BLVD & LOLA DR3002
DAVIS BLVD & MID CITIES BLVD3000
DAVIS BLVD & PRECINCT LINE RD3000
GLENVIEW DR & RUFE SNOW DR3000
HIGHTOWER DR & RUFE SNOW DR3000
MEADOW LAKES DR & RUFE SNOW DR3000
AMUNDSON DR & PRECINCT LINE RD2000
BOULEVARD 26 & NE LOOP 8202000
BOULEVARD 26 & NE LOOP 820 WBA2000
BOULEVARD 26 & RICHLAND PLAZA DR2000
BOULEVARD 26 & RODGER LINE2000
BOULEVARD 26 BLVD & DAVIS BLVD2000
DAVIS BLVD & MAIN ST2000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. North Richland Hills Crash Guide. North Richland Hills — Tarrant 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/north-richland-hills/

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

North Richland Hills city · Tarrant County. Reported city code 312; county codes 220. Current Census place identifier 4852356 (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 NORTH RICHLAND HILLS, 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, 122 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; 7 lack a usable road label. 586 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:25:05.675Z. 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 →