Asheville archive sources and coverage 22 annual sources · 2005–2026
Asheville Police Department · Imported Sep 27, 2026. 0 of 50,562 call records have approximate coordinates.
License: PDDL-1.0 ↗
Coverage and source details
- Asheville Police calls assigned a 2026 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
- Publisher documents a 90-day public-release delay. Latest call verified June 28, 2026 on September 27, 2026; this is not a live emergency feed.
Asheville Police Department · Imported Sep 27, 2026. 0 of 103,185 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2025 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 99,206 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2024 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 104,332 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2023 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher epoch timestamps preserve its encoded calendar date. Local-hour timezone conversion is not established for this archive.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 93,076 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2022 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- These archives encode Eastern local call time as UTC epochs; calendar dates are normalized to America/New_York.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 97,624 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2021 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- These archives encode Eastern local call time as UTC epochs; calendar dates are normalized to America/New_York.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 128,107 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2020 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- These archives encode Eastern local call time as UTC epochs; calendar dates are normalized to America/New_York.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 137,384 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2019 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 125,283 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2018 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 119,877 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2017 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 112,803 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2016 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 115,005 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2015 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 111,924 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2014 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 114,014 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2013 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 110,391 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2012 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 107,861 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2011 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 107,771 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2010 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 109,781 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2009 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 112,221 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2008 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 112,261 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2007 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 107,601 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2006 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is a fixed-width YYYYMMDDHHMMSS string, preserved as a calendar date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Asheville Police Department · Imported Sep 27, 2026. 0 of 106,192 call records have approximate coordinates.
Coverage and source details
- Asheville Police calls assigned a 2005 incident number only, not crimes or all Buncombe County calls. Annual tables can overlap: filtering by the call ID's encoded year prevents cross-year duplication.
- Published call records are not unique calls: one call ID can have multiple recorded times or classifications. Only distinct call-ID/time/type tuples are counted; no incident or offense total is inferred.
- Mandatory upstream DISTINCT over the allowed call ID, time, and classification. Exact addresses, call dispositions, narratives, and person-level fields are excluded.
- Publisher Call_Time is an ISO-format local clock string without a timezone offset; preserve its date.
- Historical annual archive, not a current feed. Source classification and timestamp conventions can change between years.
Reports are not convictions. Calls for service are not confirmed crimes. Location precision follows the publisher, with additional rounding where needed. How to read the data →