Police Department

Reported crimes, annual

Violent crimesProperty crimesincidents/year
010,00020,00030,00040,000200020032006200920122015201820212024

Source: CA DOJ OpenJustice, Crimes & Clearances. 738 facts, 18 metrics, 1985–2025. Chart starts at 2000; the series runs from 1985 and per-offense counts (homicide, rape, robbery, assault, burglary, vehicle theft) are in the CSV. CSV

CA DOJ adopted the FBI's revised, broader rape definition with 2014 data, so violent-crime totals before and after 2014 count rape differently. These are OPD's official annual submissions to the state; the weekly report counts below use a different method (one most-severe offense per incident, unaudited) and do not match them exactly.

Weekly Part 1 crime, citywide

All Part 1 crimesincidents/week
02004006008001,0002017201820192020202120222023202420252026
Violent crime indexincidents/week
0501001502002017201820192020202120222023202420252026

Source: OPD weekly crime report PDFs. 992 facts, 2 metrics, 2016–2026. Citywide weekly counts as charted; counts also exist for police areas 1–6 and as year-to-date totals (see CSV). Most reports before 2017 have image-only tables that are not extracted, and the 2016 reports that were extracted carry no dated weekly column, so this weekly series begins in 2017. CSV

What these terms mean (as OPD's weekly reports define them)

Part 1 crimes are the eight offense categories in the report's table: homicide, aggravated assault, rape and robbery (violent), plus burglary, motor vehicle theft, larceny and arson (property). "All Part 1 crimes" is the table's Total row — the sum of all eight. The Violent Crime Index is the report's own subtotal, defined on the report as "homicide, aggravated assault, rape, robbery".

The reports are hierarchy-based: totals reflect one offense (the most severe) per incident. Totals include attempts, except homicides. OPD marks these statistics unaudited and states they are not the figures it reports to the FBI's Uniform Crime Reporting program.

Measurement change: reports before February 21, 2022 print a single homicide row (Penal Code 187(a)). From that date the table also lists "all other" homicides (justified, accidental, or manslaughter by negligence) and the Violent Crime Index includes them, so the index counts slightly more deaths from 2022 on.

Violent offenses, weekly

Plotted separately; weekly counts range from 0–3 homicides to 20–60 robberies.

Homicideincidents/week
024682017201820192020202120222023202420252026
Rapeincidents/week
02468102017201820192020202120222023202420252026
Robberyincidents/week
0204060801002017201820192020202120222023202420252026
Aggravated assaultincidents/week
0204060801002017201820192020202120222023202420252026

Source: OPD weekly crime report PDFs. 1,984 facts, 4 metrics, 2016–2026. Citywide weekly counts as charted. CSV

Property offenses, annual totals

BurglaryMotor vehicle theftLarcenyArsonincidents/year
010,00020,00030,00040,0002017201820192020202120222023202420252026

Not plotted: 2016 (13 reports, the latest dated 12 December 2016). The corpus holds only part of that year's weekly reports, against 41–53 per year from 2017 on, and the last one's year-to-date column stops before year-end, so it is not an annual total and would sit mid-chart as though it were one. The figures are in the CSV.

Each year's figure is the last year-to-date total the weekly reports published that year, not a sum of their weekly columns. The reports are run by date of occurrence and state that crime reporting and data entry can run behind, so each week's own column counts only the crimes entered by the time that report ran; the year-to-date column continues to fill in. On the 2022 reports the weekly columns sum to 1,626 burglaries while the same reports' year-to-date column ends the year at 11,508.

Bars run 2017–2026. The last bar is partial: 2026 is in progress; its latest weekly report is dated 26 July 2026.

These counts are not comparable to the CA DOJ figures charted above. OPD counts a break-in to a vehicle as burglary; DOJ's UCR classification counts it as larceny, so OPD's burglary runs several times DOJ's and its larceny runs below DOJ's.

Source: OPD weekly crime report PDFs. 1,988 facts, 4 metrics, 2016–2026. Citywide year-to-date totals as charted. CSV

Clearances reported to CA DOJ, as a share of crimes reported to CA DOJ

HomicideViolent crimesRobberyBurglary% of reported crimes reported cleared
02040608019851990199620012006201120162021

This is the share of crimes reported to CA DOJ that OPD also reported to CA DOJ as cleared, per calendar year — a reporting ratio, not an audited solve rate. The reported clearance counts themselves collapse over the series: robbery clearances reported fall from 880 in 1985 to 147 in 2025; burglary clearances reported fall from 1,051 in 1985 to 7 in 2025. CA DOJ's statewide clearance rates over the same years stay roughly flat — about 28–31% for robbery and about 10% for burglary, which puts Oakland's recent figures more than an order of magnitude below the state. Whether that reflects clearance activity, OPD's reporting of clearances to the state, or both is not established here. Clearances can also lag the year of the offense.

Omitted rather than plotted as zero: 1995. In 1995 the file records 0 robbery clearances against 3,880 reported robberies; 0 burglary clearances against 7,030 reported burglaries, and the violent-crime clearance column equals the homicide column exactly (56), so only homicide clearances were reported. The offense counts for the year are themselves usable, so they stay in the charts above; only the clearance ratios are dropped.

Arrests, Alameda County (county context, not OPD)

Alameda County — totalarrests/year, Alameda County
025,00050,00075,000100,000125,0001980198519901995200020052010201520202025
Alameda County — felonyAlameda County — misdemeanorarrests/year, Alameda County
025,00050,00075,000100,000125,0001980198519901995200020052010201520202025

These are Alameda County arrests, not Oakland Police Department arrests. CA DOJ publishes its arrest file by county only — the file carries no city or agency column — so no Oakland-agency arrest series exists in this source. The county's population is several times Oakland's, so these counts are county context and cannot be read as OPD activity.

The 1995 figure (55,024 arrests countywide, against 91,671 in 1994 and 79,535 in 1996) is published by the DOJ as-is. The dip is countywide across all reporting agencies; no cause is established here.

Source: CA DOJ OpenJustice arrest data (county level). 138 facts, 3 metrics, 1980–2025. Geography: Alameda County. CSV

Deaths in custody

Deathsdeaths/year
0246810198019851990199520002005201020152024

Source: CA DOJ death-in-custody reporting. 42 facts, 1 metric, 1980–2025. Years without a bar have no Oakland records in the DOJ file. CSV

Hate crime events

Eventsevents/year
0102030200120042007201020132016201920222025

Source: CA DOJ hate crime data. 25 facts, 1 metric, 2001–2025. One bar per year; years without a bar have no Oakland records in the DOJ file. CSV

Use of force incidents

2017201820202021202320242025
Incidents2115213

Why this series starts in 2017 and the counts are single digits

These are incidents reported to the CA DOJ's URSUS use-of-force collection, created by Government Code section 12525.2 (AB 71) with statewide reporting starting in 2016 — no comparable state data exists earlier. URSUS covers only the most serious incidents: those involving the discharge of a firearm at a person, or force resulting in serious bodily injury or death (of a civilian or an officer). Uses of force below that threshold are not reported to this dataset, which is why annual counts are single digits. Years with no qualifying Oakland incidents in the DOJ files (2016, 2019, 2022) have no column above — the table therefore begins at 2017.

Source: CA DOJ URSUS use-of-force reporting. 7 facts, 1 metric, 2017–2025. CSV

Negotiated Settlement Agreement compliance

In compliancePartial complianceNot in compliance% of tasks tracked
020406080100200320122014201620172018201920212023

One bar per monitor report; segments are the share of that report's tracked tasks found in, partially in, or not in compliance. Reports track varying task sets (8–50 tasks) across eras: OPD self-report tables 2003–05, the full monitor era, ~22 active tasks 2010–15, and the 8 remaining tasks in the sustainability period. Bars below 100% mean some tracked tasks received no verdict in that report (early reports left most tasks as “progressing”).

Reports without a printed summary table (most 2010–2015 quarterly reports) are tallied here from their per-task verdict statements, counting sub-tasks; those tallies can rate compliance higher than the monitor's own top-level summary — e.g. the April 2010 report tallies 20 of 27 verdicts in compliance while its text states full compliance with 10 of the 22 active tasks. Per-task verdicts are in the CSV.

Source: Independent monitor reports (Allen v. City of Oakland). 1,776 facts, 154 metrics, 2003–2025. CSV

No independent anchor exists for this series: Monitor is the sole publisher; only the internal category-sum check is available.. No independent anchor exists for this series: The monitor is the sole publisher of its own compliance findings; no independent source restates them. The available check is internal: the printed categories must sum to the printed denominator.. No independent anchor exists for this series: Monitor is the sole publisher; only the internal category-sum check is available.. No independent anchor exists for this series: Monitor is the sole publisher; only the internal category-sum check is available..

Stops

Persons stopped, annual (RIPA records)

Persons stoppedpersons stopped/year
05,00010,00015,00020,00025,000201920202021202220232024

These count persons stopped, not stops. The RIPA record-level files carry one record per person stopped, so a stop of two people is two records, and the same individual stopped repeatedly counts once for each stop. The perceived-race breakdown sums to this total exactly in every year shown (2019–2024), confirming the one-record-per-person basis.

Source: CA DOJ RIPA record-level stop files, OPD only. 6 facts, 1 metric, 2019–2024. CSV

Persons stopped by perceived race (RIPA records)

BlackHispanic/LatinoWhiteAsianpersons stopped/year
05,00010,00015,000201920202021202220232024

Charted apart from the total above: a total and its breakdown on one axis compress the breakdown. The four largest perceived-race groups are shown; the remaining groups and the totals are in the CSV.

Source: CA DOJ RIPA record-level stop files, OPD only. 24 facts, 4 metrics, 2019–2024. CSV

Persons stopped per 1,000 residents of each group (RIPA records)

BlackHispanic/LatinoWhiteAsianpersons stopped per 1,000 residents
05010015020192020202120222023

Each group's RIPA persons-stopped count divided by its Census ACS population, ×1,000, for the groups with a census series (Black, Hispanic/Latino, White, Asian). Denominators are resident population; the numerator includes non-residents stopped in Oakland. RIPA records perceived race, the ACS self-reported race. Ends at the last ACS year available.

Why the pre- and post-RIPA stop series are not comparable

The 2013–2017 figures come from OPD's own stop-data collection, built for the Negotiated Settlement Agreement and analyzed in OPD's reports with Stanford researchers; OPD defined the race categories and which stops were recorded. The 2019+ figures are from the Racial and Identity Profiling Act (RIPA, AB 953) collection: a standardized statewide dataset reported to the CA DOJ, one record per person stopped, with race recorded as the officer's perception. Categories, scope, and methodology differ between the two programs, so no continuous series is drawn across 2018 (Oakland's first full RIPA year is 2019).

2013–2017 stop data (pre-RIPA)

20132014201520162017
All stops27,99133,22937,96332,56931,528
African American16,54219,05922,50320,03219,185
Hispanic4,8396,1017,4986,5906,855
White3,8014,6134,3293,2562,805
Asian1,9052,3142,4841,6481,553
Other9041,1421,1491,0431,130

No 2016 column: the 2016–2017 stop-data report prints a race table for 2017 only, and no standalone 2016 annual report is in the corpus. Mid-year reports (January–June counts) are not extracted into these annual figures.

Source: OPD stop-data report PDFs (Stanford SPARQ era). 46 facts, 16 metrics, 2013–2017. CSV

No independent anchor exists for this series: No independent publisher of pre-RIPA OPD stop counts; the check is the report's own Grand Total cross-foot (stops.py validate(), 1% tolerance).. No independent anchor exists for this series: The slide prints the drop but not the two levels it came from, so there is nothing on the page to cross-foot against and no external publisher.. No independent anchor exists for this series: Printed shares on a slide; the only check is that the race shares sum to roughly 100%, and the slide prints only three of the five categories.. No independent anchor exists for this series: No independent publisher of OPD's pre-RIPA stop counts exists. The only available check is the document's own arithmetic: stops.py validate() requires the race rows to sum to the printed Grand Total within 1%.. No independent anchor exists for this series: A one-off figure quoted in a research report; no external publisher restates it. The corpus's own corroboration is that documents 4421 and 4423 print the identical sentence..

Budget

20142015201620172020202120222023
Adopted — Police Department204.2219.7235.6242.5318.7330.1335.8342.4
201820192020202120222023
Proposed (FY2017–19)274.3291.0
Adopted — Police Commission4.14.34.55.8

$ millions. The adopted figures appear in the source under two labels — “Police Department” (FY2014–15, FY2020–21 files) and “Police” (FY2016–17, FY2022–23 files) — with no overlapping years, so they are merged into one row. FY2018–19 exist only as proposed budgets. The Police Commission is budgeted separately.

What “adopted”, “proposed”, and “actual” mean

Proposed = the spending plan the Mayor submits to the City Council. Adopted = the appropriation the City Council approves when it passes the budget — an authorization to spend, set before the fiscal year begins, not a record of what was spent. Actual = spending as reported after the fact in audited financial statements (ACFRs). Oakland budgets in two-year cycles; fiscal years here are labeled by their end year (FY2022–23 → 2023). Amounts are department totals across all funds unless noted.

General Fund actual spendingAdopted budget (all funds)$ millions
0100200300400199820012004200720102013201620192022

Adopted = the department's adopted appropriation across all funds (Open Budget Oakland, dollars). GF actual = General Fund spending only (City Auditor compiled financials / ACFRs, reported in thousands; series ends at FY2021). Different fund scopes and accounting bases — the gap between the lines reflects both.

Source: City Auditor compiled financials / ACFRs (actuals), Open Budget Oakland (adopted). 32 facts, 3 metrics, 1998–2023. CSV

No independent anchor exists for this series: Open Budget Oakland is a community re-publication of the city's budget files with no second publisher of the same aggregates. Phase 2's available check is a band comparison against the budget books (budget.book.*) where the years overlap, not an equality..

Payroll

Wages

Wages$ millions
0501001502002502015201620172018201920202021202220232024

Overtime

Overtime$ millions
02040602015201620172018201920202021202220232024

Charted separately: overtime is 15.5–24.5% of total wages in the years shown (the source's total-wages figure includes overtime).

Source: California State Controller. 30 facts, 3 metrics, 2015–2024. CSV

State Controller payroll figures are calendar-year (January–December) totals. The budget and ACFR figures elsewhere on this page are July–June fiscal years labeled by their end year, so the two are on different bases and the years are not comparable.