PoliceCensus

Home / States / North Carolina / Roanoke Rapids Police Department

Roanoke Rapids Police Department

City agency in Halifax, North Carolina, United States. Reports crime data to the FBI, and has done since 2019.

ORI
NC0420200
Type
City
County
Halifax
State
North Carolina (NC)
FBI reporting
Reporting since 2019-01-01
Location
36.2514, -77.6448

Workforce

As reported to the FBI for 2025, covering a population of 14,422.

31Sworn officers
4Civilian staff
2.43Employees per 1,000 people
14,422Population served
YearOfficersCiviliansPopulation servedPer 1,000
202531414,4222.43
202436414,4972.76
202332414,6942.45
202232415,0252.40
202134414,0462.71
202036414,1782.82
201934614,3542.79
201836714,6642.93
201737515,0832.78
201639415,2732.82
201537315,4432.59
201437415,6022.63

Officer and civilian counts are full-time employees as filed by the agency in its annual return. A dash means the agency did not report that figure for that year — it does not mean zero.

Crime and clearances

Offences and clearances filed by Roanoke Rapids Police Department in its monthly returns to the FBI, added up by calendar year, 2019–2026. Violent crime and property crime are the FBI’s two categories. These are the counts as filed: Police Census does not turn them into a rate.

Violent crime
YearMonths filedOffencesClearedCleared as % of offences
20268 of 12732027.4%
2025121208570.8%
2024121307456.9%
2023121226956.6%
2022121155850.4%
2021121116760.4%
2020121499261.7%
2019121267055.6%
Property crime
YearMonths filedOffencesClearedCleared as % of offences
20268 of 1255317030.7%
20251256023341.6%
20241249420942.3%
20231264723936.9%
20221267628542.2%
20211255620136.2%
20201260521735.9%
20191270428240.1%

Reading the table. “Not reported” means the agency filed nothing for that year; it does not mean zero. A 0 is a figure the agency filed. For 2026 the FBI is still collecting: that year is not complete in the file we read, so where this agency has no 2026 figures the table says “Not yet in the FBI’s file” rather than “Not reported”. We can see that the agency is absent from the file so far; we cannot tell whether it has not filed or has not yet been published, and we do not guess. A year marked “7 of 12” adds up only the months the agency filed, so it is not a full-year total. A dash in the last column means the percentage cannot be worked out: it needs both figures, and at least one offence.

“Cleared” is the FBI file’s clearance count for the year. Clearances in a year can relate to offences from earlier years, so the percentage is not the share of that year’s offences that were solved, and it can exceed 100%. Figures are not adjusted: a year far below the agency’s neighbouring years, or a 0 beside many offences, may reflect what was submitted rather than what happened. The file does not say which, and Police Census does not guess.

Source: FBI Crime Data Explorer, summarized data for agency record NC0420200.

Arrests

Arrests made by Roanoke Rapids Police Department, all offences combined, as filed with the FBI and added up by calendar year, 2019–2026.

YearMonths filedArrests
20268 of 12265
202512467
202412595
202312607
202212786
202112684
202012644
2019121,079

“Not reported” means the agency filed nothing for that year; it does not mean zero. A year marked “7 of 12” adds up only the months filed. For 2026 the FBI is still collecting, so an absent agency reads “Not yet in the FBI’s file”: absent from the file so far, which is not the same claim as having filed nothing. Source: FBI Crime Data Explorer, arrest data for agency record NC0420200.

Bias-motivated incidents in the FBI’s file

5 incidents appear in the FBI’s hate crime file for Roanoke Rapids Police Department for 2018, as at 14 August 2026. The table lists every year from 1991 to 2025 for which the file has at least one.

Incidents appearing in the FBI’s file, as at 14 August 2026
YearIncidents appearing in the file
20185
20171
20164
20143
20121
20101
20051
20022
20011
Bias motivation recorded, in the FBI’s words, 2001–2018
Bias motivationIncidents
Anti-Black or African American9
Anti-White5
Anti-Gay (Male)2
Anti-Asian1
Anti-Other Race/Ethnicity/Ancestry1

1 of these incidents records more than one bias motivation. The FBI’s file stores those as a single list; each is shown here as its separate entries joined by “+”, and none is added to a line in the table above.

Absence from this file is not a zero. The file lists incidents that were reported to the FBI. An agency can be missing from it because it recorded none, because it did not report, or because it does not take part in the FBI’s hate crime program, and nothing Police Census holds can tell these apart. In any one year the file lists incidents for only a minority of the agencies the FBI counts as reporting.

The figures are counts of incidents as they appear in the file, as at 14 August 2026; Police Census does not turn them into a rate and does not compare them with other agencies. Offence and bias wording is the FBI’s own, unaltered. Source: FBI Crime Data Explorer, additional datasets, hate crime bulk file, agency record NC0420200.

Assaults on officers

Officers of Roanoke Rapids Police Department assaulted in the line of duty, by the weapon reported, between 1995 and 2025. These are the FBI’s own weapon categories.

Weapon reportedOfficers assaulted
Firearm10
Knife or other cutting instrument5
Hands, fists or feet235
Other weapon29
YearFirearmKnifeHands, fists, feetOther
19950142
19960020
19970012
19980160
19990022
200011111
20010071
20021030
20030022
20040160
20050081
20060051
200710111
20080170
20090040
20101040
201100100
20120060
20130071
20140030
20150010
20160030
201700110
20180020
20191080
20200080
202100375
202200101
202330196
202410133
202510140

Why there is no single total here. The FBI publishes two breakdowns of the same assaults — by weapon, and by how the officer was deployed — and nationally they do not agree: the assignment columns sum to 1,869,337 and the weapon columns to 1,744,852, and the two match on only 84% of rows. Police Census publishes the weapon breakdown as the FBI states it rather than picking one basis and calling it ‘the total’. The file’s ‘cleared’ column is not shown either: it sums higher than the assaults themselves, so it is not a subset of what is above and we have not established what it counts.

This comes from the FBI’s Law Enforcement Officers Killed and Assaulted programme. Despite the name, the file carries no officers-killed data at all — those columns are empty for every agency and every year, so this page reports assaults only and says nothing about officers killed.

LEOKA identifies agencies by name, not by the ORI used elsewhere on this site. A row was attached only where exactly one agency in that state reduces to the same base name; 78.7% of rows matched nationwide. An agency with nothing here may have reported no assaults, or may be one of the names that did not match — Police Census does not guess which.

Military surplus received

Transferred under the Department of Defense 1033 programme, which passes surplus military equipment to law enforcement agencies at no cost. Values are the Department’s original acquisition cost, not what the equipment is worth today.

$6,902Original acquisition value
9Line items received
2014–2026Years of transfers
ItemQuantityAcquisition valueMost recent
Sight,Reflex40$2,3372016-02-09
Sniper Rifle Action Barrel3$1,8042026-02-02
Illuminator,Infrared1$1,7912025-07-02
Illuminator,Integrated,Small Arms8$9702025-07-02

Source: Defense Logistics Agency, Law Enforcement Support Office, public data as at 30 June 2026. Items are grouped by description; the date shown is the most recent shipment of that item.

Also policing Halifax

Jurisdictions overlap. These agencies are also recorded against the same county, so a single address may be covered by more than one of them.

Source

Agency identity, type, jurisdiction, coordinates and reporting status are as published by the FBI Crime Data Explorer, agency record NC0420200. Police Census reproduces these values without adjustment. Where the FBI publishes nothing, this page says so rather than estimating.

Believe something on this page is wrong? Tell us at corrections@policecensus.com — every correction is published on Corrections.