North Carolina · Independent public data
North Carolina Crime

North Carolina

North Carolina
crime records.

Search the published local records below. Each source has its own date range; a recent import does not make an older source current.

Coverage is limited to the listed agencies and sources. It is not a complete regional crime count.

Explore the data

Explore published records

Asheville call records, 2016 · call records

Download this page as JSON ↗

Ask the published data

Describe the view you want.

Reset

Use a short search phrase and the publisher’s area names. Search, area, and category filters work on up to 10,000 source records at a time. Shorten the dates for busy sources.

Viewing Dec 4, 2016 – Dec 31, 2016
Stored history: Jan 1, 2016 – Dec 31, 2016. Dates follow this source’s published date basis.

Mapped locations

Location map unavailable

This publisher does not provide usable coordinates for these records. Use the published-area comparison and record locations instead.

Published geography

Areas with the most returned records

This source does not publish an area label for the selected records.

Raw record counts, not population-adjusted risk. Area names and boundaries come from the publisher. Select an area to filter the records.

Published records

8,472 matching call records

Newest first

ASSIST EOCDispatched Dec 31, 2016

ASSIST EOC

Location not provided

Record details
Source record
2016310807
Case
2016310807
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
HIT AND RUN PROPERTY DAMAGEDispatched Dec 31, 2016

HIT AND RUN PROPERTY DAMAGE

Location not provided

Record details
Source record
2016310741
Case
2016310741
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ASSIST FIRE DEPT (APD)Dispatched Dec 31, 2016

ASSIST FIRE DEPT (APD)

Location not provided

Record details
Source record
2016310609
Case
2016310609
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ANIMAL BITEDispatched Dec 31, 2016

ANIMAL BITE

Location not provided

Record details
Source record
2016310969
Case
2016310969
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CRIME PREVENTIONDispatched Dec 31, 2016

CRIME PREVENTION

Location not provided

Record details
Source record
2016310744
Case
2016310744
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
FIREWORKS (APD)Dispatched Dec 31, 2016

FIREWORKS (APD)

Location not provided

Record details
Source record
2016310767
Case
2016310767
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
TRAFFIC STOPDispatched Dec 31, 2016

TRAFFIC STOP

Location not provided

Record details
Source record
2016310899
Case
2016310899
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
LARCENY MOTOR VEHICLEDispatched Dec 31, 2016

LARCENY MOTOR VEHICLE

Location not provided

Record details
Source record
2016310943
Case
2016310943
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
SPECIAL ASSIGNMENTDispatched Dec 31, 2016

SPECIAL ASSIGNMENT

Location not provided

Record details
Source record
2016310411
Case
2016310411
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
BUSINESS ALARMDispatched Dec 31, 2016

BUSINESS ALARM

Location not provided

Record details
Source record
2016310777
Case
2016310777
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
BUSINESS ALARMDispatched Dec 31, 2016

BUSINESS ALARM

Location not provided

Record details
Source record
2016310334
Case
2016310334
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ASSIST MOTORISTDispatched Dec 31, 2016

ASSIST MOTORIST

Location not provided

Record details
Source record
2016310605
Case
2016310605
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ANIMAL CRUELTYDispatched Dec 31, 2016

ANIMAL CRUELTY

Location not provided

Record details
Source record
2016310916
Case
2016310916
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CRIME PREVENTIONDispatched Dec 31, 2016

CRIME PREVENTION

Location not provided

Record details
Source record
2016310859
Case
2016310859
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
MVA PDDispatched Dec 31, 2016

MVA PD

Location not provided

Record details
Source record
2016310363
Case
2016310363
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
(Z)SUICIDE OVERDOSEDispatched Dec 31, 2016

(Z)SUICIDE OVERDOSE

Location not provided

Record details
Source record
2016310462
Case
2016310462
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
LARCENY MOTOR VEHICLEDispatched Dec 31, 2016

LARCENY MOTOR VEHICLE

Location not provided

Record details
Source record
2016310893
Case
2016310893
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
TRAFFIC STOPDispatched Dec 31, 2016

TRAFFIC STOP

Location not provided

Record details
Source record
2016310921
Case
2016310921
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CRIME PREVENTIONDispatched Dec 31, 2016

CRIME PREVENTION

Location not provided

Record details
Source record
2016310959
Case
2016310959
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
WELFARE CHECKDispatched Dec 31, 2016

WELFARE CHECK

Location not provided

Record details
Source record
2016310956
Case
2016310956
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
FIREWORKS (APD)Dispatched Dec 31, 2016

FIREWORKS (APD)

Location not provided

Record details
Source record
2016310789
Case
2016310789
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ASSIST EOCDispatched Dec 31, 2016

ASSIST EOC

Location not provided

Record details
Source record
2016310904
Case
2016310904
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CRIME PREVENTIONDispatched Dec 31, 2016

CRIME PREVENTION

Location not provided

Record details
Source record
2016310797
Case
2016310797
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
HIT AND RUN PROPERTY DAMAGEDispatched Dec 31, 2016

HIT AND RUN PROPERTY DAMAGE

Location not provided

Record details
Source record
2016310440
Case
2016310440
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
RAPEDispatched Dec 31, 2016

RAPE

Location not provided

Record details
Source record
2016310765
Case
2016310765
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
LARCENY REPORTDispatched Dec 31, 2016

LARCENY REPORT

Location not provided

Record details
Source record
2016310942
Case
2016310942
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
WARRANT SERVICEDispatched Dec 31, 2016

WARRANT SERVICE

Location not provided

Record details
Source record
2016310721
Case
2016310721
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
FIREWORKS (APD)Dispatched Dec 31, 2016

FIREWORKS (APD)

Location not provided

Record details
Source record
2016310854
Case
2016310854
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
BUSINESS ALARMDispatched Dec 31, 2016

BUSINESS ALARM

Location not provided

Record details
Source record
2016310766
Case
2016310766
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CIVIL DISTURBANCEDispatched Dec 31, 2016

CIVIL DISTURBANCE

Location not provided

Record details
Source record
2016310369
Case
2016310369
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
BELONGINGSDispatched Dec 31, 2016

BELONGINGS

Location not provided

Record details
Source record
2016310879
Case
2016310879
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CRIME PREVENTIONDispatched Dec 31, 2016

CRIME PREVENTION

Location not provided

Record details
Source record
2016310876
Case
2016310876
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ANIMAL CARCASDispatched Dec 31, 2016

ANIMAL CARCAS

Location not provided

Record details
Source record
2016310968
Case
2016310968
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CIVIL DISTURBANCEDispatched Dec 31, 2016

CIVIL DISTURBANCE

Location not provided

Record details
Source record
2016310621
Case
2016310621
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
DRIVING WHILE IMPAIREDDispatched Dec 31, 2016

DRIVING WHILE IMPAIRED

Location not provided

Record details
Source record
2016310243
Case
2016310243
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
MVA PDDispatched Dec 31, 2016

MVA PD

Location not provided

Record details
Source record
2016310242
Case
2016310242
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CIVIL DISTURBANCEDispatched Dec 31, 2016

CIVIL DISTURBANCE

Location not provided

Record details
Source record
2016310560
Case
2016310560
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
BUSINESS ALARMDispatched Dec 31, 2016

BUSINESS ALARM

Location not provided

Record details
Source record
2016310241
Case
2016310241
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
SUSPICIOUS VEHICLEDispatched Dec 31, 2016

SUSPICIOUS VEHICLE

Location not provided

Record details
Source record
2016310831
Case
2016310831
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
GUN DISCHARGEDispatched Dec 31, 2016

GUN DISCHARGE

Location not provided

Record details
Source record
2016310823
Case
2016310823
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
TRAFFIC STOPDispatched Dec 31, 2016

TRAFFIC STOP

Location not provided

Record details
Source record
2016310239
Case
2016310239
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
SUSPICIOUS PERSONDispatched Dec 31, 2016

SUSPICIOUS PERSON

Location not provided

Record details
Source record
2016310260
Case
2016310260
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
BUSINESS ALARMDispatched Dec 31, 2016

BUSINESS ALARM

Location not provided

Record details
Source record
2016310642
Case
2016310642
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CONTACT PUBLICDispatched Dec 31, 2016

CONTACT PUBLIC

Location not provided

Record details
Source record
2016310611
Case
2016310611
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
ID PICTURES AND PRINTSDispatched Dec 31, 2016

ID PICTURES AND PRINTS

Location not provided

Record details
Source record
2016310338
Case
2016310338
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
CHECK BUSINESSDispatched Dec 31, 2016

CHECK BUSINESS

Location not provided

Record details
Source record
2016310315
Case
2016310315
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
TRAFFIC STOPDispatched Dec 31, 2016

TRAFFIC STOP

Location not provided

Record details
Source record
2016310814
Case
2016310814
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
MVA PDDispatched Dec 31, 2016

MVA PD

Location not provided

Record details
Source record
2016310596
Case
2016310596
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
TRAFFIC STOPDispatched Dec 31, 2016

TRAFFIC STOP

Location not provided

Record details
Source record
2016310935
Case
2016310935
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records
DRIVING WHILE IMPAIREDDispatched Dec 31, 2016

DRIVING WHILE IMPAIRED

Location not provided

Record details
Source record
2016310528
Case
2016310528
Published location
Location not provided
Approximate coordinates
Coordinates not provided
Counting unit
call records

Annual crime statistics

Official annual totals are separate from the record feed. County reporting totals overlap individual agencies. Subtotals overlap their component offenses. These figures are never added together here.

Showing statewide statistics. Search for a city, agency, or county to browse its published years.

Browse all

Browse permanent annual reports by area and year →

1 matching source, area, and year table · 1 shown

North Carolina

Statewide · Jan 1, 2025 – Dec 31, 2025 · Original source ↗

North Carolina 2025 crime statistics →

FBI statewide annual estimates. Includes estimation for missing agency reporting; not a collection of mapped incidents.

OffensePublished countMeasure
Property crime Subtotal199,308estimated offenses
Theft142,471estimated offenses
Violent crime Subtotal36,991estimated offenses
Burglary34,035estimated offenses
Aggravated assault28,770estimated offenses
Vehicle theft22,802estimated offenses
Robbery4,573estimated offenses
Rape2,925estimated offenses
Murder and nonnegligent manslaughter723estimated offenses

Where the data comes from

Sources and coverage

Asheville reported offenses

151,119 offense records storedArchive: Jan 1, 2013 – Sep 18, 2026Last published record: Sep 18, 2026Reported dates · Browse latest 28 days →

Cary published crime offenses

26,270 incident-offense records storedArchive: Dec 31, 2020 – Jul 26, 2026Last published record: Jul 26, 2026Occurrence dates · Browse latest 28 days →

Chapel Hill published incident offenses

122,506 incident-offense records storedArchive: Jan 15, 1991 – May 31, 2026Last published record: May 31, 2026Occurrence dates · Browse latest 28 days →

Charlotte-Mecklenburg reported incidents

871,916 incident records storedArchive: Jan 1, 2017 – Sep 25, 2026Last published record: Sep 25, 2026Reported dates · Browse latest 28 days →

Durham reported offenses

137,971 offense records storedArchive: Jan 1, 2022 – Sep 25, 2026Last published record: Sep 25, 2026Reported dates · Browse latest 28 days →

Fayetteville offenses against people

68,708 offense records storedArchive: Jan 1, 2010 – Sep 26, 2026Last published record: Sep 26, 2026Occurrence dates · Browse latest 28 days →

Fayetteville property offenses

241,896 offense records storedArchive: Jan 1, 2010 – Sep 26, 2026Last published record: Sep 26, 2026Occurrence dates · Browse latest 28 days →

Fayetteville public-order and other society offenses

33,319 offense records storedArchive: Jan 1, 2010 – Sep 26, 2026Last published record: Sep 26, 2026Occurrence dates · Browse latest 28 days →

Greensboro historical reported offenses

147,070 offense records storedArchive: Oct 1, 2020 – Oct 6, 2025Historical source · Last published record: Oct 6, 2025Reported dates · Browse latest 28 days →

Raleigh reported crime offenses

642,785 offense records storedArchive: Jun 1, 2014 – Sep 27, 2026Last published record: Sep 27, 2026Reported dates · Browse latest 28 days →
Asheville call-record archives 22 annual sources · 2005–2026 · Viewing 2016

Choose a source year to browse its latest 28 available days, then use the date controls for older records. These are published call records, not crimes or unique calls; a call may have multiple times or classifications.

Asheville reported offenses ↗

Asheville Police Department · Imported Sep 27, 2026. 0 of 151,119 offense records have approximate coordinates.

Coverage and source details
  • Asheville's public dashboard offense view only, not all Buncombe County or North Carolina. Reported date, not occurrence date.
  • The overlapping Crimes_public and APD Public Incidents mirrors are deliberately not appended.
  • Police classifications and public-release filters can change. Long historical counts should not be treated as a consistent measure of all crime.
  • Exact address, geometry, officer, narrative, and relationship fields are excluded. Offense IDs are published offense references, not unique case counts.
  • Official public city source; attribute Asheville Police. No specific license is asserted for this offense layer.

Cary published crime offenses ↗

Cary Police Department · Imported Sep 27, 2026. 0 of 26,270 incident-offense records have approximate coordinates.

License: CC0-1.0 ↗

Coverage and source details
  • Cary only, not all Wake County or North Carolina. Selected published offense classes; sexual assaults, crimes involving juveniles, and some active investigations are omitted by the publisher.
  • Catalog refreshed September 27, 2026, but latest occurrence verified July 26, 2026. Catalog refresh is not record freshness.
  • Mandatory upstream grouping uses only the allowed incident/date/offense/district fields; duplicate person-expanded rows are not fetched. Group multiplicities are checked against the source row count, not labeled as additional offenses.
  • No coordinates are published in this schema. Apartment/subdivision data and other person-sensitive or unnecessary fields are excluded.
  • Undated records are excluded from the dated series. CC0 1.0 public-domain dedication; source attribution is retained.

Chapel Hill published incident offenses ↗

Town of Chapel Hill Police Department · Imported Sep 27, 2026. 0 of 122,506 incident-offense records have approximate coordinates.

License: ODbL-1.0 ↗

Coverage and source details
  • Contains information from Town of Chapel Hill Police Department, made available under the Open Database License (ODbL) 1.0. Keep this component attributed and separately identifiable; redistribution of a derived database must retain ODbL requirements.
  • Mandatory upstream DISTINCT over only incident ID, occurrence date, offense and city. Victim demographics, person-level fields, exact addresses, and coordinates are excluded from every request. Raw source row IDs are not selected.
  • One row represents a distinct published incident/date/offense/city combination, not one person or necessarily one unique incident.
  • Latest occurrence verified May 31, 2026; do not label this a current September feed. Earliest legacy records date to 1991 and do not establish continuous coverage since then.
  • Metadata has conflicting local-time and UTC conventions. Preserve publisher-encoded calendar dates and do not infer local-hour patterns. Chapel Hill coverage only, not the entire county or state.

Charlotte-Mecklenburg reported incidents ↗

Charlotte-Mecklenburg Police Department · Imported Sep 27, 2026. 871,872 of 871,916 incident records have approximate coordinates.

Coverage and source details
  • One published incident with its highest NIBRS offense, not every offense in each case. Reported-date basis. Charlotte-Mecklenburg contribution only, not statewide coverage.
  • Includes non-criminal and unfounded reports; incident records are not confirmed crimes. The publisher excludes 800-series NIBRS codes from criminal-incident analysis.
  • Only explicitly public coordinates retained. Exact LOCATION field is excluded.
  • The public server intermittently rejects valid identical queries. Only verified transient application errors receive bounded retries; source counts and unique IDs must still reconcile before publication.

Durham reported offenses ↗

Durham Police Department · Imported Sep 27, 2026. 0 of 137,971 offense records have approximate coordinates.

Coverage and source details
  • This is a nonspatial table. No coordinates may be inferred from ADDRESS2. Reported-date window, not occurrence date. State page covers Durham only for this source.

Fayetteville offenses against people ↗

Fayetteville Police Department · Imported Sep 27, 2026. 68,430 of 68,708 offense records have approximate coordinates.

Coverage and source details
  • Fayetteville Police offense records, not victim or person records. Multiple offenses can share a case number; this is not all Cumberland County or North Carolina.
  • Dates use Eastern local calendar days. Query bounds are publisher-local; feature epochs are UTC. Verified winter and summer boundary tests reconcile the source's missing timezone metadata.
  • Exact address, apartment, premise, and all person-level records are excluded. Published coordinates are further rounded.
  • Official city open-data source; attribute Fayetteville Police. No specific machine-readable reuse license was provided.

Fayetteville property offenses ↗

Fayetteville Police Department · Imported Sep 27, 2026. 241,209 of 241,896 offense records have approximate coordinates.

Coverage and source details
  • Fayetteville Police property-offense records only, not all Cumberland County or North Carolina. Several offenses may share a case number.
  • Dates use Eastern local calendar days. Query bounds are publisher-local; feature epochs are UTC. Verified winter and summer boundary tests reconcile the source's missing timezone metadata.
  • Exact address, apartment, premise, and all person-level records are excluded. Published coordinates are further rounded.
  • Official city open-data source; attribute Fayetteville Police. No specific machine-readable reuse license was provided.

Fayetteville public-order and other society offenses ↗

Fayetteville Police Department · Imported Sep 27, 2026. 32,865 of 33,319 offense records have approximate coordinates.

Coverage and source details
  • Fayetteville Police crimes-against-society offense records only, not all Cumberland County or North Carolina. Multiple offenses may share a case number.
  • Dates use Eastern local calendar days. Query bounds are publisher-local; feature epochs are UTC. Verified winter and summer boundary tests reconcile the source's missing timezone metadata.
  • Exact address, apartment, premise, and all person-level records are excluded. Published coordinates are further rounded.
  • Official city open-data source; attribute Fayetteville Police. No specific machine-readable reuse license was provided.

Greensboro historical reported offenses ↗

Greensboro Police Department · Imported Sep 27, 2026. 0 of 147,070 offense records have approximate coordinates.

Coverage and source details
  • Historical Greensboro city offense archive, not all Guilford County or North Carolina. Latest report date verified October 6, 2025; not a live current feed.
  • Reported date is used. Offense records may share an incident ID and are not unique incidents or convictions.
  • Exact addresses, unverified coordinates, victim counts, and person-level datasets are excluded.
  • Official Open Gate City source; attribute Greensboro Police. No specific machine-readable license was supplied.

Raleigh reported crime offenses ↗

Raleigh Police Department · Imported Sep 27, 2026. 406,398 of 642,785 offense records have approximate coordinates.

Coverage and source details
  • Dates preserve the publisher-encoded calendar date. Local-hour conversion is not established and is not inferred from the city.
  • Reported date, not occurrence date. Raleigh contributor only; does not imply statewide coverage.
Asheville archive sources and coverage 22 annual sources · 2005–2026

Asheville call records, 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 call records, 2025 ↗

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 call records, 2024 ↗

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 call records, 2023 ↗

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 call records, 2022 ↗

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 call records, 2021 ↗

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 call records, 2020 ↗

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 call records, 2019 ↗

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 call records, 2018 ↗

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 call records, 2017 ↗

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 call records, 2016 ↗

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 call records, 2015 ↗

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 call records, 2014 ↗

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 call records, 2013 ↗

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 call records, 2012 ↗

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 call records, 2011 ↗

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 call records, 2010 ↗

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 call records, 2009 ↗

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 call records, 2008 ↗

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 call records, 2007 ↗

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 call records, 2006 ↗

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 call records, 2005 ↗

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 →