Chicago police reports — 2025-01

January 2025 as an open-data slice

Each of the 17,638 rows is a published CPD incident whose report date falls in 2025-01. Primary types are unfiltered. This page will not invent a violent-crime share. Filter IUCR labels on the overlay if you need one type.

New Year's Day, the inauguration-week civic calendar, and winter weather are not packet facts. If those days produced reports, they are inside 17,638 when the report date is in January. Do not treat 17,638 as a holiday-week statistic.

Report date defines membership. Occurrence date can sit in 2024 for a report taken in January 2025. This packet does not count that lag. Read the table columns on the overlay.

January 2025 opens the calendar year in this Chicago index at 17,638 CPD incidents with report dates in 2025-01. New Year's week is inside that total only when the report date falls in January; this page does not publish a holiday cell. A report taken in January can describe an occurrence in 2024. Keep those columns distinct. The Chicago hub is the parent view when 2025-01 is the wrong filter.

City-wide, with official area names on rows

Community area names on January rows are official city geography when CPD filled the field. The 17,638 headline is not one area. Blank areas stay blank.

Block-level locations are offset public records. They are not street-number identifications of a resident or a venue. A dense January cluster is a set of report pins, not a neighborhood indictment.

If you need one official community area, filter the 2025-01 table. Do not paste 17,638 into a story about a single area.

On the 2025-01 overlay, official community area names are the geography this Chicago index supports when CPD published them. The 17,638 headline is not Austin, not Near North Side, and not any other single official area. Researchers who need one area should filter the table and caption the subset as a subset. Block-level coordinates, when present, are offset public-record locations. They do not identify a resident, a school, or a storefront by street number. CPD incident rows can lack an area; those rows still sit inside 17,638. LocalCrimeVault does not impute a community area to complete a pin map. Festival-corridor or lakefront density, if you observe it after sorting, is a table observation about report locations, not a packet fact about event crime. Keep 17,638 attached to Chicago as a whole for 2025-01.

How the January table behaves

Sort 17,638 rows by date, type, or community area. Arrest flags are not convictions. Missing geocodes stay missing. LocalCrimeVault does not impute them.

Later harvests can add late-submitted January reports or revise rows CPD has corrected. Cite 17,638 as the current indexed count for 2025-01 report dates.

The 2025-01 table is the working surface for these 17,638 rows. Sort by date, by IUCR primary type, or by geography. An arrest field, if shown, is still an attribute of a CPD report. It is not a charging decision and not a guilty finding. Unfounded or later-reclassified rows can remain until the source extract changes. Missing coordinates stay missing. OEMC CAD calls that never became incident numbers sit outside the total. Unreported events never enter 17,638. Sealed or restricted records that CPD does not publish never enter 17,638. If a type filter reduces the table, the caption should say the slice is no longer the city-wide 2025-01 headline. LocalCrimeVault does not reclassify charges inside the 17,638 mix.

Limits of the January total

Seventeen thousand six hundred thirty-eight is not OEMC call volume, not unique offenders, and not court dispositions. Unreported events never enter the extract. CAD calls that never became incident numbers sit outside 17,638.

This page does not compare January 2025 to December 2024 or to February 2025. Those integers are not in this packet.

Chicago hub and how to cite 2025-01

The 2025-01 overlay is the live table for these 17,638 rows. The Chicago hub holds other months, type pages, and community-area pages. Use the hub when January is the wrong window.

Citation: 17,638 Chicago Police Department incidents with a report date in 2025-01, indexed on LocalCrimeVault from city open data. Counts are reports, not convictions. LocalCrimeVault does not reclassify CPD charges.

A durable citation for this page names the agency, the date field, the month, the integer, and the indexer: 2025 CPD incidents with a report date in 2025-01, indexed on LocalCrimeVault from city open data. Add that counts are reports, not convictions, and that report date can differ from occurrence date. If you filtered the overlay to one type or one community area, say so; that subset is no longer 2025. Later harvests can move the integer as CPD adds late-submitted rows or revises old ones. Do not mix this 2025-01 total with another month's count on a chart unless that other integer is actually in hand from its own packet. This file's facts support 17,638 only.

Documenting the 2025-01 harvest for Chicago

Chicago 2025-01 remains 2025 indexed CPD incidents with report dates in 2025-01 in this harvest. The overlay is the live table. The city hub is the parent view for other months and for type or geography pages that are not limited to 2025-01. Keep the reports-not-convictions clause next to 2025. LocalCrimeVault does not dramatize individual cases and does not turn 2025 into a ranking of neighborhoods, boroughs, or divisions.

Open data lags live dispatch. 2025 is the published extract LocalCrimeVault indexed for 2025-01, not a live CAD feed and not a promise that a portal query tomorrow returns the same integer. Record the month label 2025-01 next to 2025 if you republish the figure so a later snapshot is not silently mixed into the same sentence.

Questions

How many Chicago CPD incidents are indexed for January 2025?

LocalCrimeVault currently indexes 17,638 incidents with a report date in 2025-01. The source is Chicago Police Department open data. The mix includes every IUCR primary type in that window. The figure is a police-report count, not a conviction count. 17,638 is the current indexed total for Chicago report dates in 2025-01, drawn from Chicago Police Department records on city open data. LocalCrimeVault does not reclassify charges. Later harvests can still move the integer.

Does 17,638 include a New Year's Eve or New Year's Day breakout?

No. Packet facts give one month total. Holiday-week reports, if they exist in the extract, are inside 17,638 when the report date falls in 2025-01. Filter the overlay by date. This page does not publish a New Year's subtotal. The packet facts give one month total for Chicago in 2025-01. Event-day isolation requires a date filter on the overlay. This page does not invent a subtotal that is not in the facts. Counts remain reports, not convictions.

Is the January total a community-area figure?

No. 17,638 is city-wide. Official community area names appear when CPD published them. Some rows lack an area. Use table filters for a single official area. 17,638 is city-wide for Chicago. Official community area names appear when the source published them. Some rows lack geography. Filter the overlay for a single official community area; do not treat the headline as that area's volume. Block-level pins are not household identifications.

Are January 2025 incident rows convictions?

No. They are police reports. Arrest flags are not court findings. LocalCrimeVault indexes CPD incidents by report date and does not reclassify charges. Court outcomes live elsewhere. Public incident rows for Chicago in 2025-01 are Chicago Police Department reports across IUCR primary types. An arrest field is not a court finding. LocalCrimeVault indexes by report date and does not treat 17,638 as a guilty-finding total. Court outcomes live in a different system.