Police reports in New York City

What the 400,500 New York City reports measure

The 400,500 figure is a count of incident records in the NYPD open-data feed that LocalCrimeVault indexes for New York City. Each row is a police report NYPD published with an offense classification and a borough field. The number is not a Census population, a victimization survey, or a conviction tally. It is the size of the public table for New York City in this snapshot.

Dates in the extract run from March 25, 2024 through December 31, 2025. Open data is not a live 911 feed. Events can appear in other NYPD products before they land as open-data rows, and NYPD can revise older records in a later file. Treat 400,500 as the published extract LocalCrimeVault indexed, then re-pull if you need a new as-of date.

New York City geography on this site follows borough labels as they appear on the incident extract. Those borough pages use the same parent file of 400,500 reports. Precincts, community districts, and neighborhood tabulation areas are different geographies and will not add to 400,500 unless they were the field NYPD published.

How to read the arrest field on this extract

Of 400,500 New York City reports, 394,883 carry an arrest field in this index (about 98.6 percent). Agency feeds define that field differently. On this snapshot the flag is densely populated, which is a fact about the extract, not a claim that nearly every complaint produced a court case. An arrest field is still not a conviction. This packet does not include a usable domestic-flag total for New York City, so this page does not invent one.

LocalCrimeVault does not dramatize individual cases. The overlay and the incident table are a public-record baseline for journalists, residents, and analysts who already know that open data lags live dispatch and omits sealed or restricted records.

How to read the New York City incident table

The city hub lists the rows behind the 400,500 total. Sort and filter there for the published offense classification, date, and borough rather than treating the headline as a story. Location fields on open data are often offset. They are not a promise that a named address was involved.

Offense-type pages under New York City split the same 400,500 parent file by NYPD's published offense labels, including truncated statute names as they appear in the source (for example shortened public-order strings). Borough pages split the file by borough name. Child pages should still cite 400,500 as the city denominator when they quote a share.

Reports are not convictions

NYPD open data records what officers documented, not what a prosecutor charged or a court decided. Unfounded reports and later recodes can remain as rows until the source file changes. Treat every New York City total on this page as a report count. If you need a disposition, this is the wrong dataset.

The arrest field (394,883, about 98.6 percent of 400,500) is densely populated on this snapshot. That is a fact about how the extract stores the flag, not a claim that nearly every complaint produced a court case. Cite 394,883 as an arrest-field count, with the March 25, 2024–December 31, 2025 window attached.

Source and update caveats

Source: NYPD incidents via NYC Open Data, indexed on LocalCrimeVault. NYPD 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 the city portal. Record the 2024–2025 date span (March 25, 2024 to December 31, 2025) next to 400,500 if you cite the extract.

Published offense classifications and borough names on child pages partition this same 400,500 file. If a type filter or a borough filter reduces the table, the caption should say the slice is no longer the city headline. LocalCrimeVault does not reclassify NYPD charges and does not fill blank geocodes.

Where to go next

Stay on the New York City crime hub for the citywide table of 400,500 reports. Use the offense-type index when you need NYPD offense labels instead of a map. Pair any borough count with this 400,500 parent so the share is against the same file. Keep the reports-not-convictions clause next to the number.

Researchers who export rows are still looking at police reports. Location fields may be offset. Some values are blank in source data. 400,500 is the indexed snapshot for New York City, not a promise that a query on the portal tomorrow returns the same integer or the same 394,883 arrest-field count.

Questions

How many crime reports are in the New York City index?

LocalCrimeVault indexes 400,500 NYPD incident reports, with extract dates from March 25, 2024 through December 31, 2025. 394,883 rows carry an arrest field in this snapshot. The numbers count published police reports, not convictions, unique offenders, or a population-based crime rate.

Are New York City crime numbers convictions?

No. The 400,500 total is a count of NYPD incident records in NYC Open Data. 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 New York City, not for guilt or sentencing.

What dates does the New York City extract cover?

The indexed snapshot used for this page runs from March 25, 2024 through December 31, 2025. NYPD can add late-submitted rows or correct old ones, so a later harvest can move the 400,500 total. Cite the date span with the count if you republish the figure.

How is New York City geography labeled?

This site files New York City incidents under borough names as published on the extract. Those borough tables partition the same 400,500 city reports. Precinct maps and informal neighborhood names that never appear as the borough field will not match this file.