PoliceCensus

Home / States / California / San Jacinto Police Department

San Jacinto Police Department

City agency in Riverside, California, United States. Reports crime data to the FBI, and has done since 2026.

ORI
CA0331400
Type
City
County
Riverside
State
California (CA)
FBI reporting
Reporting since 2026-01-01
Location
33.782, -116.9595

Workforce

As reported to the FBI for 2015, covering a population of 47,022.

1Sworn officers
0Civilian staff
0.02Employees per 1,000 people
47,022Population served
YearOfficersCiviliansPopulation servedPer 1,000
20151047,0220.02
20141046,2160.02
20111044,7190.02
200632830,5251.31
200531528,2291.28
200429527,2401.25
200326925,9591.35
200224924,6531.34
2001241024,2211.40
200024923,7791.39
1999241024,6861.38
1998241024,5371.39

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 San Jacinto 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 1218411160.3%
2025121789653.9%
2024121426042.3%
20231223010746.5%
2022121114540.5%
2021Not reported
202012983939.8%
2019121082220.4%
Property crime
YearMonths filedOffencesClearedCleared as % of offences
20268 of 12377328.5%
202512847657.7%
202412974646.6%
2023121,230635.1%
2022121,226524.2%
2021Not reported
2020121,466765.2%
2019121,6421046.3%

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 CA0331400.

Arrests

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

YearMonths filedArrests
20268 of 12702
2025120
2024120
202312945
202212987
2021Not reported
2020121,510
2019121,503

“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. A 0 is the figure as filed: the file does not distinguish an agency that made no arrests from one that did not submit them, and Police Census cannot either. Source: FBI Crime Data Explorer, arrest data for agency record CA0331400.

Bias-motivated incidents in the FBI’s file

2 incidents appear in the FBI’s hate crime file for San Jacinto 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
20182
20171
20151
20101
20091
20073
20051
20042
Bias motivation recorded, in the FBI’s words, 2004–2018
Bias motivationIncidents
Anti-Black or African American7
Anti-Other Religion2
Anti-Gay (Male)1
Anti-Jewish1
Anti-White1

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 CA0331400.

Deaths during encounters with this agency

2 people have died during an encounter with San Jacinto Police Department between 2004 and 2004, according to the two datasets named below.

2Deaths recorded
4.25Per 100,000 people policed
2004–2004Period covered
Recorded causeDeaths
Vehicle2

What this figure is and is not. It counts deaths recorded as occurring during an encounter with this agency. It is not a finding of wrongdoing, and a death being recorded here says nothing about whether it was lawful. Many involve armed confrontations; some involve none. Police Census publishes counts only and does not name the people who died.

Source: every one of these records comes from Fatal Encounters, which records deaths from 2000–2021. They are not official statistics, and no federal database records this comprehensively. See Deaths for how these records are compiled.

Assaults on officers

Officers of San Jacinto 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
Firearm4
Knife or other cutting instrument2
Hands, fists or feet112
Other weapon16
YearFirearmKnifeHands, fists, feetOther
19950126
19960062
199700120
19980070
19990171
20000050
20010070
20021060
20030010
20050020
20061072
20070010
20080040
20090040
20100032
20110060
20120011
20130020
20140030
20152030
20160010
20170050
20180030
20190010
20200021
20220010
20230061
20240020
20250020

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.

Also policing Riverside

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 CA0331400. 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.