New York City police reports — 2025-12

Read 500 as the current December harvest

The 500 rows are NYPD incidents whose report date falls in 2025-12 in this index, across published offense classifications. Open-data months can arrive sparse and can be backfilled. This page does not invent a missing remainder, because no other December total is in the packet. Cite 500 as what LocalCrimeVault currently holds for New York City in 2025-12.

Holiday-week calendars, New Year's Eve, and year-end retail hours are not packet subtotals. If those days produced reports in this extract, they sit inside 500 when the report date is in December. Do not treat 500 as a Times Square statistic.

Report date defines membership. Complaint date or occurrence date, when NYPD filled a separate column, can sit outside 2025-12. This harvest does not split those columns. Read the overlay headers.

New York City in 2025-12 is 500 indexed NYPD incidents with report dates in that month in this harvest. That is a small current extract, not a claim that the city went quiet. Later NYC Open Data pulls can add rows. Holiday weeks are not isolated. Borough filters, if used, produce a subset of 500, not a second headline. Precincts are a different geography than borough. Counts are reports, not convictions.

Borough labels on a small monthly slice

New York City geography on this site follows borough labels as they appear on the incident extract. The 500 headline is city-wide. It is not Brooklyn, not Manhattan, and not a precinct total. Precincts, community districts, and neighborhood tabulation areas are different systems.

A thin December harvest is not a claim that other boroughs vanished. It is a claim about the current extract. Filter the overlay by borough if a borough field is present; do not quote 500 as one borough's volume.

Location fields on NYC Open Data are often offset. They are not a promise that a named address was involved. Block-level pins are not household identifications.

On the 2025-12 overlay, borough labels are the geography this New York City index supports when NYPD published them. The 500 headline is not Brooklyn, not Manhattan, not Queens, not the Bronx, and not Staten Island as a standalone total. Precincts, community districts, and neighborhood tabulation areas are different systems and will not add to 500 unless the borough field is also on the row. Location fields on NYC Open Data are often offset. They are not a promise that a named address was involved. A dense cluster on the 2025-12 map is a set of report pins, not a building accusation. Blank borough fields still count toward 500. Filtering them out shrinks the visible set. Stay with the borough field and the city-wide 500 when you cite this page.

How to use the 2025-12 overlay

Sort the 500 rows by date, offense classification, or borough when those columns exist. Arrest fields, if shown, are still attributes of reports. They are not guilty findings.

Because 500 is an indexed count, a later harvest can add late-submitted December reports or drop rows NYPD has revised. Re-check the overlay if you need a newer as-of date.

The 2025-12 table is the working surface for these 500 rows. Sort by date, by published offense classification, or by geography. An arrest field, if shown, is still an attribute of a NYPD 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. Events that never became NYC Open Data rows sit outside the total. Unreported events never enter 500. Sealed or restricted records that NYPD does not publish never enter 500. If a type filter reduces the table, the caption should say the slice is no longer the city-wide 2025-12 headline. LocalCrimeVault does not reclassify charges inside the 500 mix.

What 500 cannot answer

It cannot compare December 2025 to November 2025, because that other integer is not in this packet. It cannot convert 500 into 911 call volume, unique defendants, or court dispositions.

Unreported events never enter the extract. Sealed or restricted records NYPD does not publish never enter the 500. CAD events that never became open-data rows sit outside the total.

New York City hub and citation

The 2025-12 overlay is the live table for these 500 rows. The New York City hub is the parent city view for other months, offense types, and borough pages. Use the hub when 2025-12 is the wrong window, or when you need a type filter that is not limited to this harvest.

Citation: 500 NYPD incidents with a report date in 2025-12, indexed on LocalCrimeVault from NYC Open Data. Add that the figure is the current harvest, that later extracts can move, and that counts are reports, not convictions.

A durable citation for this page names the agency, the date field, the month, the integer, and the indexer: 2025 NYPD incidents with a report date in 2025-12, indexed on LocalCrimeVault from NYC 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 borough, say so; that subset is no longer 2025. Later harvests can move the integer as NYPD adds late-submitted rows or revises old ones. Do not mix this 2025-12 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 500 only.

Documenting the 2025-12 harvest for New York City

New York City 2025-12 remains 2025 indexed NYPD incidents with report dates in 2025-12 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-12. 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-12, not a live CAD feed and not a promise that a portal query tomorrow returns the same integer. Record the month label 2025-12 next to 2025 if you republish the figure so a later snapshot is not silently mixed into the same sentence.

Questions

How many NYPD incidents are indexed for December 2025?

LocalCrimeVault currently indexes 500 incidents with a report date in 2025-12 for New York City. The source is NYC Open Data. The figure counts police reports in this harvest, not convictions. Later extracts can still move the integer. 500 is the current indexed total for New York City report dates in 2025-12, drawn from NYPD records on NYC Open Data. LocalCrimeVault does not reclassify charges. Later harvests can still move the integer.

Is 500 a complete closed month for New York City?

This page treats 500 as the current indexed count for 2025-12 report dates. Open-data extracts can add late rows or revise old ones. Cite the figure with that caveat. It remains a city-wide report total, not a borough total and not a conviction total.

Does 500 belong to one borough?

No. It is a New York City city-wide monthly total as indexed. Borough names appear when NYPD published them. Precinct maps are a different geography. Do not treat 500 as Brooklyn or Manhattan volume. 500 is city-wide for New York City. Borough names appear when the source published them. Some rows lack geography. Filter the overlay for a single borough; do not treat the headline as that area's volume. Block-level pins are not household identifications.

Are December 2025 NYPD rows court outcomes?

No. They are police reports. Arrest fields are not convictions. LocalCrimeVault indexes NYPD incidents by report date and does not reclassify charges. Court files live in a different system. Public incident rows for New York City in 2025-12 are NYPD reports across published offense classifications. An arrest field is not a court finding. LocalCrimeVault indexes by report date and does not treat 500 as a guilty-finding total. Court outcomes live in a different system.