Police reports in Chicago

What the 410,083 Chicago reports measure

The 410,083 figure is a count of incident records in the CPD open-data feed that LocalCrimeVault indexes for Chicago. Each row is a police report: a documented event CPD published with enough location and type fields to land in this city extract. The number is not a resident population, a victimization survey, or a conviction tally. It is the size of the public table for Chicago in this snapshot.

Dates in the extract run from July 16, 2024 through May 30, 2026. Open data is not a live dispatch feed. A scanner or a 911 tracker can show events that have not yet appeared as Socrata rows, and CPD can republish older records into a later file. Treat 410,083 as the published extract LocalCrimeVault indexed, then re-pull if you need a new as-of date.

Chicago community-area names are how this site slices geography under the city hub. Those area pages use the same parent file of 410,083 reports. Beats, districts, and wards are different geographies. If a map you saw used beats, it will not match this city total even when the street looks familiar.

Arrest and domestic fields are still reports

Of 410,083 Chicago reports, 62,890 carry an arrest field in this index (about 15.3 percent). That is a flag on a police-report row, not a prosecutor filing and not a guilty finding. A missing arrest field does not prove that nothing happened; a present arrest field does not prove a court outcome. 77,122 reports carry a domestic field (about 18.8 percent of 410,083). That split is how CPD published the extract, not a household census.

LocalCrimeVault does not add narrative color to individual cases. The overlay and the incident table are for people who need a public-record baseline: journalists checking a beat, residents reading official volume, and analysts who already know that open data lags live CAD and omits sealed or restricted records.

How to read the Chicago incident table

The city hub lists the rows behind the 410,083 total. Sort and filter there for CPD primary type, date, and community area rather than treating the headline as a story. Block-level fields, where published, are coarse on purpose. They are not street-number addresses and are not proof that a named business or resident was involved.

Offense-type pages under Chicago split the same 410,083 parent file by IUCR primary type. Neighborhood pages split it by official community-area name. Those child pages should still cite 410,083 as the city denominator when they quote a share. Mixing in FBI tables, OEMC call logs, or a vendor dashboard that used a different cut will break the share math.

Reports are not convictions

CPD open data records what officers documented, not what a prosecutor charged or a court decided. Duplicate calls, unfounded reports, and incidents later reclassified can still appear as rows. Treat every Chicago total on this page as a report count. If you need a disposition, this is the wrong dataset.

The arrest field (62,890) and the domestic field (77,122) are still attributes of reports. They do not convert 410,083 into a clearance rate or a household survey. Cite them as flags on the public extract, with the July 16, 2024–May 30, 2026 window attached, so a later snapshot is not silently mixed into the same sentence.

Source and update caveats

Source: Chicago Police Department incidents via the city open-data portal (Socrata), indexed on LocalCrimeVault. CPD can revise rows after publication. Counts on this page match the index snapshot used to build the packet, not a live query you run later on data.cityofchicago.org. Record the 2024–2026 date span (July 16, 2024 to May 30, 2026) next to 410,083 if you cite the extract.

IUCR primary types and community-area names on child pages partition this same 410,083 file. If a type filter or an area filter reduces the table, the caption should say the slice is no longer the city headline. LocalCrimeVault does not reclassify CPD charges and does not fill blank geocodes.

Where to go next

Stay on the Chicago crime hub for the citywide table of 410,083 reports. Use the offense-type index when you need IUCR categories instead of a map. Pair any neighborhood count with this 410,083 parent so the share is against the same file. Keep the reports-not-convictions clause on the same screen as the number.

Researchers who export rows are still looking at police reports. Block ranges are coarse. Some community-area values are blank in source data. 410,083 is the indexed snapshot for Chicago, not a promise that a query on the portal tomorrow returns the same integer, the same 62,890 arrest-field count, or the same 77,122 domestic-field count.

Questions

How many crime reports are in the Chicago index?

LocalCrimeVault indexes 410,083 Chicago Police incident reports, with extract dates from July 16, 2024 through May 30, 2026. 62,890 rows carry an arrest field and 77,122 carry a domestic field. The numbers count published police reports, not convictions, unique offenders, or a population-based crime rate.

Are Chicago crime numbers convictions?

No. The 410,083 total is a count of CPD incident records in the city's open-data portal. A report can be unfounded, reclassified, or never charged. Court outcomes live in a different system. Use this page for public police-report volume in Chicago, not for guilt or sentencing.

What dates does the Chicago extract cover?

The indexed snapshot used for this page runs from July 16, 2024 through May 30, 2026. CPD can add late-submitted rows or correct old ones, so a later harvest can move the 410,083 total. Cite the date span with the count if you republish the figure.

Where can I see Chicago offense types?

Open the Chicago crime hub for the citywide table, then use the offense-type index for IUCR primary categories that partition the same 410,083 reports. LocalCrimeVault does not reclassify CPD charges. Type pages remain police-report counts, not conviction tallies.