Seattle Police
Call volumeOutcomesHow long it tookHow long it took, in full

Property Destruction (Damage)

Property Destruction (Damage) calls over time: volume, outcomes, and response speed

Property Destruction: Call Volume

Call volume is the number of events logged in the Seattle Police Department’s Computer-Aided Dispatch (CAD) system. It counts calls from the public (by 911, phone, text or alarm) as well as officer-initiated activity, once per event, grouped by the call type assigned when the call was dispatched, before any investigation. It is not the same as the number of crimes reported.

Included: Every event logged in CAD: calls from the public and events officers logged themselves (11% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
03,0006,0002009: 3,881 property destruction (damage) calls logged in CAD2010: 5,549 property destruction (damage) calls logged in CAD2011: 5,335 property destruction (damage) calls logged in CAD2012: 5,315 property destruction (damage) calls logged in CAD2013: 5,053 property destruction (damage) calls logged in CAD2014: 5,028 property destruction (damage) calls logged in CAD2015: 4,873 property destruction (damage) calls logged in CAD2016: 4,964 property destruction (damage) calls logged in CAD2017: 4,805 property destruction (damage) calls logged in CAD2018: 4,705 property destruction (damage) calls logged in CAD2019: 3,889 property destruction (damage) calls logged in CAD2020: 4,045 property destruction (damage) calls logged in CAD2021: 4,352 property destruction (damage) calls logged in CAD2022: 4,114 property destruction (damage) calls logged in CAD2023: 4,347 property destruction (damage) calls logged in CAD2024: 4,222 property destruction (damage) calls logged in CAD2025: 3,861 property destruction (damage) calls logged in CAD2026: 2,523 property destruction (damage) calls logged in CAD2009n=3,8812011n=5,3352013n=5,0532015n=4,8732017n=4,8052019n=3,8892021n=4,3522023n=4,3472025n=3,8612026n=2,523
property destruction (damage) calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodProperty destruction (damage) calls logged in CAD
20093,881
20105,549
20115,335
20125,315
20135,053
20145,028
20154,873
20164,964
20174,805
20184,705
20193,889
20204,045
20214,352
20224,114
20234,347
20244,222
20253,861
20262,523
Property Destruction Calls Are Down 30% From Their 2010 PeakSeattle Police logged 5,549 property destruction calls in 2010 and 3,861 in 2025, the most recent full year.

Property Destruction: What Happened When Officers Responded

Outcomes show how each call ended, based on the disposition officers recorded when the call was closed: an arrest or citation, a report taken with no arrest, resolved on scene, unable to locate (officers could not find the incident or the person who called), or other (unfounded or cancelled). Each bar shows the share of that period’s calls.

Included: Every event, called in or officer-initiated, using the disposition recorded when the event was closed. Excluded: Nothing.

Swipe sideways to see the full chart →
100%50%0%2009 · Arrest / citation: 4.7%2009 · Report taken, no arrest: 75.3%2009 · Resolved on scene: 12.2%2009 · Unable to locate: 3.8%2009 · Other (unfounded / cancelled): 4.0%2010 · Arrest / citation: 5.2%2010 · Report taken, no arrest: 78.0%2010 · Resolved on scene: 10.8%2010 · Unable to locate: 3.6%2010 · Other (unfounded / cancelled): 2.4%2011 · Arrest / citation: 4.9%2011 · Report taken, no arrest: 78.1%2011 · Resolved on scene: 10.7%2011 · Unable to locate: 3.9%2011 · Other (unfounded / cancelled): 2.3%2012 · Arrest / citation: 5.3%2012 · Report taken, no arrest: 76.6%2012 · Resolved on scene: 11.4%2012 · Unable to locate: 4.1%2012 · Other (unfounded / cancelled): 2.6%2013 · Arrest / citation: 5.4%2013 · Report taken, no arrest: 77.2%2013 · Resolved on scene: 11.0%2013 · Unable to locate: 4.7%2013 · Other (unfounded / cancelled): 1.7%2014 · Arrest / citation: 4.9%2014 · Report taken, no arrest: 77.1%2014 · Resolved on scene: 10.1%2014 · Unable to locate: 6.4%2014 · Other (unfounded / cancelled): 1.5%2015 · Arrest / citation: 5.7%2015 · Report taken, no arrest: 77.8%2015 · Resolved on scene: 8.4%2015 · Unable to locate: 6.4%2015 · Other (unfounded / cancelled): 1.7%2016 · Arrest / citation: 5.4%2016 · Report taken, no arrest: 77.5%2016 · Resolved on scene: 8.8%2016 · Unable to locate: 6.7%2016 · Other (unfounded / cancelled): 1.7%2017 · Arrest / citation: 6.5%2017 · Report taken, no arrest: 76.7%2017 · Resolved on scene: 9.5%2017 · Unable to locate: 5.9%2017 · Other (unfounded / cancelled): 1.4%2018 · Arrest / citation: 6.4%2018 · Report taken, no arrest: 77.2%2018 · Resolved on scene: 8.2%2018 · Unable to locate: 6.5%2018 · Other (unfounded / cancelled): 1.7%2019 · Arrest / citation: 8.2%2019 · Report taken, no arrest: 72.7%2019 · Resolved on scene: 9.3%2019 · Unable to locate: 7.6%2019 · Other (unfounded / cancelled): 2.1%2020 · Arrest / citation: 6.6%2020 · Report taken, no arrest: 74.2%2020 · Resolved on scene: 10.3%2020 · Unable to locate: 7.4%2020 · Other (unfounded / cancelled): 1.5%2021 · Arrest / citation: 6.0%2021 · Report taken, no arrest: 74.3%2021 · Resolved on scene: 9.4%2021 · Unable to locate: 9.0%2021 · Other (unfounded / cancelled): 1.4%2022 · Arrest / citation: 6.0%2022 · Report taken, no arrest: 72.7%2022 · Resolved on scene: 9.7%2022 · Unable to locate: 10.4%2022 · Other (unfounded / cancelled): 1.2%2023 · Arrest / citation: 5.0%2023 · Report taken, no arrest: 71.3%2023 · Resolved on scene: 8.7%2023 · Unable to locate: 13.8%2023 · Other (unfounded / cancelled): 1.2%2024 · Arrest / citation: 5.0%2024 · Report taken, no arrest: 68.2%2024 · Resolved on scene: 9.4%2024 · Unable to locate: 16.7%2024 · Other (unfounded / cancelled): 0.8%2025 · Arrest / citation: 6.2%2025 · Report taken, no arrest: 67.2%2025 · Resolved on scene: 10.0%2025 · Unable to locate: 15.6%2025 · Other (unfounded / cancelled): 1.0%2026 · Arrest / citation: 6.7%2026 · Report taken, no arrest: 65.4%2026 · Resolved on scene: 9.4%2026 · Unable to locate: 17.3%2026 · Other (unfounded / cancelled): 1.2%2009n=3,8812011n=5,3352013n=5,0532015n=4,8732017n=4,8052019n=3,8892021n=4,3522023n=4,3472025n=3,8612026n=2,523
Arrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
View as table
What happened when officers responded — same numbers as the chart above
PeriodEventsArrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
20093,8814.7%75.3%12.2%3.8%4.0%
20105,5495.2%78.0%10.8%3.6%2.4%
20115,3354.9%78.1%10.7%3.9%2.3%
20125,3155.3%76.6%11.4%4.1%2.6%
20135,0535.4%77.2%11.0%4.7%1.7%
20145,0284.9%77.1%10.1%6.4%1.5%
20154,8735.7%77.8%8.4%6.4%1.7%
20164,9645.4%77.5%8.8%6.7%1.7%
20174,8056.5%76.7%9.5%5.9%1.4%
20184,7056.4%77.2%8.2%6.5%1.7%
20193,8898.2%72.7%9.3%7.6%2.1%
20204,0456.6%74.2%10.3%7.4%1.5%
20214,3526.0%74.3%9.4%9.0%1.4%
20224,1146.0%72.7%9.7%10.4%1.2%
20234,3475.0%71.3%8.7%13.8%1.2%
20244,2225.0%68.2%9.4%16.7%0.8%
20253,8616.2%67.2%10.0%15.6%1.0%
20262,5236.7%65.4%9.4%17.3%1.2%
17% of Property Destruction Calls End “Unable to Locate,” Up From 7%Report-taken outcomes moved from 78% of calls in 2016 to 65% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Property Destruction: How Long It Took

Response time is how long it took, from the moment a called-in event was queued with dispatch, until the first officer arrived on scene. Dispatch delay is the first part of that wait: the time before an officer was assigned and sent. Both lines show the average, which a small number of very long waits pull up, so it runs higher than the typical (median) call.

Included: Only events called in by the public and dispatched to an officer. The averages use those with a recorded officer arrival. The n= under each bar is the number of called-in events. Excluded: Events officers logged themselves (on view), which are 11% of property destruction events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min75 min150 min2009: 35.8 min2010: 27.8 min2011: 29.2 min2012: 36.0 min2013: 40.3 min2014: 47.7 min2015: 53.2 min2016: 55.7 min2017: 51.1 min2018: 66.6 min2019: 58.5 min2020: 50.4 min2021: 67.4 min2022: 65.7 min2023: 88.9 min2024: 119.9 min2025: 109.8 min2026: 108.9 min2009: 44.3 min2010: 35.2 min2011: 39.3 min2012: 45.7 min2013: 50.4 min2014: 57.8 min2015: 63.4 min2016: 66.5 min2017: 61.6 min2018: 77.9 min2019: 69.9 min2020: 58.9 min2021: 76.9 min2022: 75.3 min2023: 100.5 min2024: 131.5 min2025: 117.0 min2026: 117.2 min2009n=3,5082011n=4,6222013n=4,6192015n=4,3082017n=4,2082019n=3,4532021n=3,8982023n=3,8652025n=3,4822026n=2,262
Average response timeAverage dispatch delay
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20093,50835.8 min44.3 min
20105,00327.8 min35.2 min
20114,62229.2 min39.3 min
20124,74436.0 min45.7 min
20134,61940.3 min50.4 min
20144,50347.7 min57.8 min
20154,30853.2 min63.4 min
20164,37555.7 min66.5 min
20174,20851.1 min61.6 min
20184,11566.6 min77.9 min
20193,45358.5 min69.9 min
20203,53850.4 min58.9 min
20213,89867.4 min76.9 min
20223,63465.7 min75.3 min
20233,86588.9 min100.5 min
20243,710119.9 min131.5 min
20253,482109.8 min117.0 min
20262,262108.9 min117.2 min
The Average Call Waits 117 Minutes for an Officer to ArriveDespite a 22% drop in calls between 2016 and 2025, average response time has increased 76% in the past 10 years, from 66 minutes in 2016 to 117 in 2026, driven largely by dispatch delays.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

Property Destruction: How Long It Took, in Full

The same response times, broken into bands so the slowest calls are visible. Each bar shows the share of called-in events by how long the first officer took to arrive after the event was queued, including the ones that took hours. “No recorded response” means no arrival was ever logged.

Included: Only events called in by the public and dispatched to an officer, including those with no recorded arrival (shown as “No recorded response”). Excluded: Events officers logged themselves (on view), which are 11% of property destruction events, because they have no wait. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
100%50%0%2009 · No recorded response: 4.0%2009 · 0–5 min: 15.8%2009 · 5–30 min: 40.2%2009 · 30–60 min: 18.4%2009 · 1–4 hr: 19.6%2009 · 4–8 hr: 1.9%2009 · Over 8 hr: 0.1%2010 · No recorded response: 3.3%2010 · 0–5 min: 21.7%2010 · 5–30 min: 42.9%2010 · 30–60 min: 15.1%2010 · 1–4 hr: 16.2%2010 · 4–8 hr: 0.7%2010 · Over 8 hr: 0.1%2011 · No recorded response: 3.6%2011 · 0–5 min: 18.3%2011 · 5–30 min: 43.5%2011 · 30–60 min: 14.6%2011 · 1–4 hr: 18.5%2011 · 4–8 hr: 1.5%2011 · Over 8 hr: 0.0%2012 · No recorded response: 3.5%2012 · 0–5 min: 17.4%2012 · 5–30 min: 40.8%2012 · 30–60 min: 14.3%2012 · 1–4 hr: 21.9%2012 · 4–8 hr: 2.0%2012 · Over 8 hr: 0.1%2013 · No recorded response: 3.1%2013 · 0–5 min: 15.6%2013 · 5–30 min: 39.4%2013 · 30–60 min: 15.4%2013 · 1–4 hr: 24.0%2013 · 4–8 hr: 2.4%2013 · Over 8 hr: 0.2%2014 · No recorded response: 3.5%2014 · 0–5 min: 13.1%2014 · 5–30 min: 39.8%2014 · 30–60 min: 14.5%2014 · 1–4 hr: 25.0%2014 · 4–8 hr: 3.8%2014 · Over 8 hr: 0.4%2015 · No recorded response: 3.1%2015 · 0–5 min: 15.3%2015 · 5–30 min: 36.6%2015 · 30–60 min: 14.2%2015 · 1–4 hr: 25.5%2015 · 4–8 hr: 4.8%2015 · Over 8 hr: 0.5%2016 · No recorded response: 2.9%2016 · 0–5 min: 14.7%2016 · 5–30 min: 36.5%2016 · 30–60 min: 13.9%2016 · 1–4 hr: 25.9%2016 · 4–8 hr: 5.4%2016 · Over 8 hr: 0.7%2017 · No recorded response: 2.5%2017 · 0–5 min: 12.7%2017 · 5–30 min: 39.0%2017 · 30–60 min: 15.3%2017 · 1–4 hr: 25.9%2017 · 4–8 hr: 3.9%2017 · Over 8 hr: 0.6%2018 · No recorded response: 3.3%2018 · 0–5 min: 10.1%2018 · 5–30 min: 34.5%2018 · 30–60 min: 15.8%2018 · 1–4 hr: 28.2%2018 · 4–8 hr: 7.5%2018 · Over 8 hr: 0.6%2019 · No recorded response: 3.9%2019 · 0–5 min: 11.8%2019 · 5–30 min: 36.2%2019 · 30–60 min: 14.2%2019 · 1–4 hr: 28.4%2019 · 4–8 hr: 4.9%2019 · Over 8 hr: 0.7%2020 · No recorded response: 3.6%2020 · 0–5 min: 15.0%2020 · 5–30 min: 37.2%2020 · 30–60 min: 14.9%2020 · 1–4 hr: 25.2%2020 · 4–8 hr: 3.7%2020 · Over 8 hr: 0.4%2021 · No recorded response: 4.8%2021 · 0–5 min: 12.8%2021 · 5–30 min: 36.4%2021 · 30–60 min: 13.0%2021 · 1–4 hr: 25.2%2021 · 4–8 hr: 6.3%2021 · Over 8 hr: 1.4%2022 · No recorded response: 4.7%2022 · 0–5 min: 14.2%2022 · 5–30 min: 34.0%2022 · 30–60 min: 14.4%2022 · 1–4 hr: 25.6%2022 · 4–8 hr: 5.5%2022 · Over 8 hr: 1.6%2023 · No recorded response: 6.9%2023 · 0–5 min: 13.6%2023 · 5–30 min: 30.6%2023 · 30–60 min: 13.3%2023 · 1–4 hr: 25.2%2023 · 4–8 hr: 6.6%2023 · Over 8 hr: 3.8%2024 · No recorded response: 6.5%2024 · 0–5 min: 10.3%2024 · 5–30 min: 25.3%2024 · 30–60 min: 12.7%2024 · 1–4 hr: 29.1%2024 · 4–8 hr: 11.2%2024 · Over 8 hr: 5.0%2025 · No recorded response: 2.6%2025 · 0–5 min: 16.8%2025 · 5–30 min: 28.3%2025 · 30–60 min: 12.3%2025 · 1–4 hr: 25.7%2025 · 4–8 hr: 9.8%2025 · Over 8 hr: 4.5%2026 · No recorded response: 2.9%2026 · 0–5 min: 12.8%2026 · 5–30 min: 30.3%2026 · 30–60 min: 12.8%2026 · 1–4 hr: 25.7%2026 · 4–8 hr: 11.1%2026 · Over 8 hr: 4.5%2009n=3,5082011n=4,6222013n=4,6192015n=4,3082017n=4,2082019n=3,4532021n=3,8982023n=3,8652025n=3,4822026n=2,262
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in eventsNo recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
20093,5084.0%15.8%40.2%18.4%19.6%1.9%0.1%
20105,0033.3%21.7%42.9%15.1%16.2%0.7%0.1%
20114,6223.6%18.3%43.5%14.6%18.5%1.5%0.0%
20124,7443.5%17.4%40.8%14.3%21.9%2.0%0.1%
20134,6193.1%15.6%39.4%15.4%24.0%2.4%0.2%
20144,5033.5%13.1%39.8%14.5%25.0%3.8%0.4%
20154,3083.1%15.3%36.6%14.2%25.5%4.8%0.5%
20164,3752.9%14.7%36.5%13.9%25.9%5.4%0.7%
20174,2082.5%12.7%39.0%15.3%25.9%3.9%0.6%
20184,1153.3%10.1%34.5%15.8%28.2%7.5%0.6%
20193,4533.9%11.8%36.2%14.2%28.4%4.9%0.7%
20203,5383.6%15.0%37.2%14.9%25.2%3.7%0.4%
20213,8984.8%12.8%36.4%13.0%25.2%6.3%1.4%
20223,6344.7%14.2%34.0%14.4%25.6%5.5%1.6%
20233,8656.9%13.6%30.6%13.3%25.2%6.6%3.8%
20243,7106.5%10.3%25.3%12.7%29.1%11.2%5.0%
20253,4822.6%16.8%28.3%12.3%25.7%9.8%4.5%
20262,2622.9%12.8%30.3%12.8%25.7%11.1%4.5%
The Average Call Waits 109 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 109 minutes in 2026, about 2.0 times what it was in 2016. 41% of calls took more than an hour to get a response in 2026, compared with 32% in 2016.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2009 and 2026 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each year is the number of events logged that year in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.