Calendar-year view of the selected crime type.
Crime type year
Chicago Kidnapping statistics for 2016
Chicago reported 202 kidnapping incidents in 2016. That was 0.1% of the citywide total for the same year.
Reported incidents for this crime type in the selected year.
Share of Chicago’s citywide total in the same year.
Latest completed import or aggregate refresh.
Context
Year-specific category context
Additional reading notes to help interpret the statistics on this page.
For 2016, the community areas with the largest published counts for kidnapping included Chatham, Washington Heights, and Auburn Gresham.
Recent matching rows provide case-level context, but the primary reading surface for this page remains the yearly aggregate total.
Highest-volume community areas
Community areas with the largest published counts for this crime type in 2016.
Recent rows
Recent matching incidents
Recent incident rows are capped for page speed and included for context only.
| Date | Type | Block | Neighborhood | Arrest |
|---|---|---|---|---|
| December 31, 2016 | Kidnapping | 061XX S LAFLIN ST | West Englewood | No |
| December 29, 2016 | Kidnapping | 071XX S JEFFERY BLVD | South Shore | No |
| December 27, 2016 | Kidnapping | 114XX S STEWART AVE | Roseland | No |
| December 19, 2016 | Kidnapping | 026XX W 64TH ST | Chicago Lawn | No |
| December 16, 2016 | Kidnapping | 075XX S EVANS AVE | Greater Grand Crossing | No |
| December 15, 2016 | Kidnapping | 027XX W ROOSEVELT RD | North Lawndale | No |
| December 14, 2016 | Kidnapping | 054XX N MAGNOLIA AVE | Edgewater | No |
| December 12, 2016 | Kidnapping | 008XX E 63RD ST | Woodlawn | No |
| December 4, 2016 | Kidnapping | 094XX S LAFLIN ST | Washington Heights | No |
| December 2, 2016 | Kidnapping | 024XX N PULASKI RD | Logan Square | No |
| December 1, 2016 | Kidnapping | 076XX S DOBSON AVE | Greater Grand Crossing | No |
| November 28, 2016 | Kidnapping | 004XX E 75TH ST | Greater Grand Crossing | Yes |
| November 28, 2016 | Kidnapping | 045XX W 81ST ST | Ashburn | No |
| November 28, 2016 | Kidnapping | 046XX N ELSTON AVE | Irving Park | No |
| November 25, 2016 | Kidnapping | 035XX W 66TH PL | Chicago Lawn | No |
| November 23, 2016 | Kidnapping | 082XX S PEORIA ST | Auburn Gresham | No |
| November 23, 2016 | Kidnapping | 030XX E 79TH ST | South Chicago | No |
| November 22, 2016 | Kidnapping | 026XX E 79TH ST | South Chicago | No |
| November 21, 2016 | Kidnapping | 040XX W WABANSIA AVE | Humboldt Park | No |
| November 20, 2016 | Kidnapping | 091XX S LAFLIN ST | Washington Heights | No |
Explore more
Related pages
Move between citywide, map, category, neighborhood, and year-specific routes with descriptive internal links.
Important context
Methodology and caveats
These pages summarize reported public records. Use source notes and methodology before drawing comparisons.
Reported crime data can lag the real world and may exclude the most recent days.
Case classifications can change after additional investigation or administrative review.
Map coordinates are approximate because the source data is redacted to the block level.
Counts on this site summarize reported incidents and should not be treated as a complete measure of safety.
Read the methodology page for pipeline details and the about page for source notes.
Sources
Official data sources
CrimeAtlas is built from public datasets published by city agencies. Each page links back to the underlying source and the latest import timestamp.
Chicago community areas
Publisher: City of Chicago
Dataset ID: igwz-8jzy
Refresh cadence: Updated as needed
Last imported: March 12, 2026
Chicago crime incidents
Publisher: Chicago Police Department
Dataset ID: ijzp-q8t2
Refresh cadence: Daily
Last imported: March 16, 2026
Chicago neighborhood boundaries reference
Publisher: City of Chicago
Dataset ID: 9wp7-iasj
Refresh cadence: Legacy file dataset
Last imported: Not available
FAQ
Frequently asked questions
Short answers about data coverage, definitions, and how to read these pages.
Does the 2016 page include all incidents?
The annual total reflects all imported incidents for that year, while supporting tables and lists may show only the largest categories or a recent sample.
Why use yearly pages?
Year pages capture long-tail search intent and make it easier to compare one calendar year against the next.