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

Disturbance

Disturbance calls over time: volume, outcomes, and response speed

Disturbance: 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 (7% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
025,00050,0002009: 21,871 disturbance calls logged in CAD2010: 34,892 disturbance calls logged in CAD2011: 35,947 disturbance calls logged in CAD2012: 38,158 disturbance calls logged in CAD2013: 39,287 disturbance calls logged in CAD2014: 38,642 disturbance calls logged in CAD2015: 42,413 disturbance calls logged in CAD2016: 43,349 disturbance calls logged in CAD2017: 43,396 disturbance calls logged in CAD2018: 42,189 disturbance calls logged in CAD2019: 42,517 disturbance calls logged in CAD2020: 32,828 disturbance calls logged in CAD2021: 33,046 disturbance calls logged in CAD2022: 35,220 disturbance calls logged in CAD2023: 36,798 disturbance calls logged in CAD2024: 36,409 disturbance calls logged in CAD2025: 39,012 disturbance calls logged in CAD2026: 27,894 disturbance calls logged in CAD2009n=21,8712011n=35,9472013n=39,2872015n=42,4132017n=43,3962019n=42,5172021n=33,0462023n=36,7982025n=39,0122026n=27,894
disturbance calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodDisturbance calls logged in CAD
200921,871
201034,892
201135,947
201238,158
201339,287
201438,642
201542,413
201643,349
201743,396
201842,189
201942,517
202032,828
202133,046
202235,220
202336,798
202436,409
202539,012
202627,894
Disturbance Calls Are Down 10% From Their 2017 PeakSeattle Police logged 43,396 disturbance calls in 2017 and 39,012 in 2025, the most recent full year.

Disturbance: 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: 0.9%2009 · Report taken, no arrest: 7.4%2009 · Resolved on scene: 74.0%2009 · Unable to locate: 14.6%2009 · Other (unfounded / cancelled): 3.1%2010 · Arrest / citation: 0.8%2010 · Report taken, no arrest: 8.7%2010 · Resolved on scene: 72.9%2010 · Unable to locate: 14.5%2010 · Other (unfounded / cancelled): 3.2%2011 · Arrest / citation: 0.6%2011 · Report taken, no arrest: 8.9%2011 · Resolved on scene: 71.8%2011 · Unable to locate: 15.3%2011 · Other (unfounded / cancelled): 3.4%2012 · Arrest / citation: 0.4%2012 · Report taken, no arrest: 8.6%2012 · Resolved on scene: 71.8%2012 · Unable to locate: 15.8%2012 · Other (unfounded / cancelled): 3.4%2013 · Arrest / citation: 0.3%2013 · Report taken, no arrest: 8.8%2013 · Resolved on scene: 70.8%2013 · Unable to locate: 16.7%2013 · Other (unfounded / cancelled): 3.3%2014 · Arrest / citation: 0.3%2014 · Report taken, no arrest: 10.9%2014 · Resolved on scene: 65.5%2014 · Unable to locate: 19.7%2014 · Other (unfounded / cancelled): 3.6%2015 · Arrest / citation: 0.3%2015 · Report taken, no arrest: 12.2%2015 · Resolved on scene: 61.4%2015 · Unable to locate: 22.7%2015 · Other (unfounded / cancelled): 3.4%2016 · Arrest / citation: 0.3%2016 · Report taken, no arrest: 12.0%2016 · Resolved on scene: 61.6%2016 · Unable to locate: 22.4%2016 · Other (unfounded / cancelled): 3.7%2017 · Arrest / citation: 0.3%2017 · Report taken, no arrest: 11.9%2017 · Resolved on scene: 60.3%2017 · Unable to locate: 23.5%2017 · Other (unfounded / cancelled): 4.0%2018 · Arrest / citation: 0.3%2018 · Report taken, no arrest: 12.5%2018 · Resolved on scene: 56.7%2018 · Unable to locate: 26.4%2018 · Other (unfounded / cancelled): 4.1%2019 · Arrest / citation: 0.3%2019 · Report taken, no arrest: 12.3%2019 · Resolved on scene: 53.9%2019 · Unable to locate: 29.5%2019 · Other (unfounded / cancelled): 4.0%2020 · Arrest / citation: 0.7%2020 · Report taken, no arrest: 13.8%2020 · Resolved on scene: 53.0%2020 · Unable to locate: 28.0%2020 · Other (unfounded / cancelled): 4.5%2021 · Arrest / citation: 0.2%2021 · Report taken, no arrest: 14.3%2021 · Resolved on scene: 49.5%2021 · Unable to locate: 31.7%2021 · Other (unfounded / cancelled): 4.3%2022 · Arrest / citation: 0.2%2022 · Report taken, no arrest: 12.5%2022 · Resolved on scene: 46.6%2022 · Unable to locate: 37.7%2022 · Other (unfounded / cancelled): 3.0%2023 · Arrest / citation: 0.2%2023 · Report taken, no arrest: 12.8%2023 · Resolved on scene: 42.8%2023 · Unable to locate: 40.5%2023 · Other (unfounded / cancelled): 3.6%2024 · Arrest / citation: 0.2%2024 · Report taken, no arrest: 11.5%2024 · Resolved on scene: 40.7%2024 · Unable to locate: 44.5%2024 · Other (unfounded / cancelled): 3.0%2025 · Arrest / citation: 0.4%2025 · Report taken, no arrest: 10.8%2025 · Resolved on scene: 42.6%2025 · Unable to locate: 43.3%2025 · Other (unfounded / cancelled): 2.9%2026 · Arrest / citation: 0.4%2026 · Report taken, no arrest: 11.4%2026 · Resolved on scene: 40.2%2026 · Unable to locate: 45.3%2026 · Other (unfounded / cancelled): 2.8%2009n=21,8712011n=35,9472013n=39,2872015n=42,4132017n=43,3962019n=42,5172021n=33,0462023n=36,7982025n=39,0122026n=27,894
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)
200921,8710.9%7.4%74.0%14.6%3.1%
201034,8920.8%8.7%72.9%14.5%3.2%
201135,9470.6%8.9%71.8%15.3%3.4%
201238,1580.4%8.6%71.8%15.8%3.4%
201339,2870.3%8.8%70.8%16.7%3.3%
201438,6420.3%10.9%65.5%19.7%3.6%
201542,4130.3%12.2%61.4%22.7%3.4%
201643,3490.3%12.0%61.6%22.4%3.7%
201743,3960.3%11.9%60.3%23.5%4.0%
201842,1890.3%12.5%56.7%26.4%4.1%
201942,5170.3%12.3%53.9%29.5%4.0%
202032,8280.7%13.8%53.0%28.0%4.5%
202133,0460.2%14.3%49.5%31.7%4.3%
202235,2200.2%12.5%46.6%37.7%3.0%
202336,7980.2%12.8%42.8%40.5%3.6%
202436,4090.2%11.5%40.7%44.5%3.0%
202539,0120.4%10.8%42.6%43.3%2.9%
202627,8940.4%11.4%40.2%45.3%2.8%
45% of Disturbance Calls End “Unable to Locate,” Up From 22%Report-taken outcomes moved from 12% of calls in 2016 to 11% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Disturbance: 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 7% of disturbance 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 min60 min120 min2009: 28.1 min2010: 20.8 min2011: 19.7 min2012: 24.2 min2013: 25.0 min2014: 27.0 min2015: 34.1 min2016: 28.3 min2017: 29.8 min2018: 39.0 min2019: 38.2 min2020: 30.1 min2021: 47.7 min2022: 55.5 min2023: 70.8 min2024: 104.7 min2025: 98.6 min2026: 94.2 min2009: 32.7 min2010: 25.9 min2011: 25.0 min2012: 29.6 min2013: 30.3 min2014: 32.6 min2015: 39.6 min2016: 34.7 min2017: 36.3 min2018: 45.9 min2019: 44.7 min2020: 38.5 min2021: 55.7 min2022: 61.6 min2023: 77.0 min2024: 109.3 min2025: 104.7 min2026: 101.3 min2009n=19,6132011n=32,1462013n=35,7952015n=39,0552017n=40,1682019n=39,4312021n=31,5632023n=35,0462025n=37,3812026n=26,717
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
200919,61328.1 min32.7 min
201030,87620.8 min25.9 min
201132,14619.7 min25.0 min
201234,53624.2 min29.6 min
201335,79525.0 min30.3 min
201435,51027.0 min32.6 min
201539,05534.1 min39.6 min
201639,86028.3 min34.7 min
201740,16829.8 min36.3 min
201839,26739.0 min45.9 min
201939,43138.2 min44.7 min
202030,66530.1 min38.5 min
202131,56347.7 min55.7 min
202233,24755.5 min61.6 min
202335,04670.8 min77.0 min
202434,491104.7 min109.3 min
202537,38198.6 min104.7 min
202626,71794.2 min101.3 min
The Average Call Waits 101 Minutes for an Officer to ArriveDespite a 10% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 35 minutes in 2016 to 101 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.

Disturbance: 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 7% of disturbance 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: 7.2%2009 · 0–5 min: 19.6%2009 · 5–30 min: 45.4%2009 · 30–60 min: 13.0%2009 · 1–4 hr: 13.8%2009 · 4–8 hr: 0.9%2009 · Over 8 hr: 0.0%2010 · No recorded response: 6.9%2010 · 0–5 min: 24.2%2010 · 5–30 min: 46.5%2010 · 30–60 min: 11.5%2010 · 1–4 hr: 10.4%2010 · 4–8 hr: 0.5%2010 · Over 8 hr: 0.0%2011 · No recorded response: 7.1%2011 · 0–5 min: 24.6%2011 · 5–30 min: 47.1%2011 · 30–60 min: 10.8%2011 · 1–4 hr: 9.8%2011 · 4–8 hr: 0.5%2011 · Over 8 hr: 0.0%2012 · No recorded response: 7.4%2012 · 0–5 min: 22.4%2012 · 5–30 min: 45.6%2012 · 30–60 min: 11.5%2012 · 1–4 hr: 12.2%2012 · 4–8 hr: 0.9%2012 · Over 8 hr: 0.0%2013 · No recorded response: 6.9%2013 · 0–5 min: 22.4%2013 · 5–30 min: 45.4%2013 · 30–60 min: 11.7%2013 · 1–4 hr: 12.6%2013 · 4–8 hr: 0.9%2013 · Over 8 hr: 0.0%2014 · No recorded response: 7.8%2014 · 0–5 min: 20.4%2014 · 5–30 min: 45.7%2014 · 30–60 min: 11.7%2014 · 1–4 hr: 13.2%2014 · 4–8 hr: 1.2%2014 · Over 8 hr: 0.1%2015 · No recorded response: 7.4%2015 · 0–5 min: 19.5%2015 · 5–30 min: 43.6%2015 · 30–60 min: 11.8%2015 · 1–4 hr: 15.5%2015 · 4–8 hr: 2.0%2015 · Over 8 hr: 0.2%2016 · No recorded response: 6.9%2016 · 0–5 min: 20.1%2016 · 5–30 min: 45.9%2016 · 30–60 min: 11.5%2016 · 1–4 hr: 14.0%2016 · 4–8 hr: 1.4%2016 · Over 8 hr: 0.1%2017 · No recorded response: 7.4%2017 · 0–5 min: 17.9%2017 · 5–30 min: 45.7%2017 · 30–60 min: 12.3%2017 · 1–4 hr: 15.2%2017 · 4–8 hr: 1.4%2017 · Over 8 hr: 0.1%2018 · No recorded response: 8.3%2018 · 0–5 min: 16.1%2018 · 5–30 min: 42.2%2018 · 30–60 min: 12.5%2018 · 1–4 hr: 18.2%2018 · 4–8 hr: 2.5%2018 · Over 8 hr: 0.3%2019 · No recorded response: 9.1%2019 · 0–5 min: 16.1%2019 · 5–30 min: 41.9%2019 · 30–60 min: 12.4%2019 · 1–4 hr: 18.0%2019 · 4–8 hr: 2.3%2019 · Over 8 hr: 0.2%2020 · No recorded response: 8.9%2020 · 0–5 min: 16.2%2020 · 5–30 min: 47.0%2020 · 30–60 min: 11.1%2020 · 1–4 hr: 14.7%2020 · 4–8 hr: 1.7%2020 · Over 8 hr: 0.2%2021 · No recorded response: 10.5%2021 · 0–5 min: 12.4%2021 · 5–30 min: 42.5%2021 · 30–60 min: 11.2%2021 · 1–4 hr: 19.2%2021 · 4–8 hr: 3.4%2021 · Over 8 hr: 0.8%2022 · No recorded response: 12.5%2022 · 0–5 min: 11.9%2022 · 5–30 min: 38.9%2022 · 30–60 min: 11.5%2022 · 1–4 hr: 20.2%2022 · 4–8 hr: 4.2%2022 · Over 8 hr: 0.8%2023 · No recorded response: 13.4%2023 · 0–5 min: 11.1%2023 · 5–30 min: 37.7%2023 · 30–60 min: 10.3%2023 · 1–4 hr: 19.8%2023 · 4–8 hr: 5.8%2023 · Over 8 hr: 1.8%2024 · No recorded response: 12.5%2024 · 0–5 min: 8.6%2024 · 5–30 min: 31.7%2024 · 30–60 min: 10.6%2024 · 1–4 hr: 24.5%2024 · 4–8 hr: 8.5%2024 · Over 8 hr: 3.6%2025 · No recorded response: 10.9%2025 · 0–5 min: 9.2%2025 · 5–30 min: 31.7%2025 · 30–60 min: 11.3%2025 · 1–4 hr: 25.4%2025 · 4–8 hr: 8.2%2025 · Over 8 hr: 3.3%2026 · No recorded response: 9.3%2026 · 0–5 min: 9.3%2026 · 5–30 min: 33.2%2026 · 30–60 min: 11.6%2026 · 1–4 hr: 24.8%2026 · 4–8 hr: 8.5%2026 · Over 8 hr: 3.2%2009n=19,6132011n=32,1462013n=35,7952015n=39,0552017n=40,1682019n=39,4312021n=31,5632023n=35,0462025n=37,3812026n=26,717
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
200919,6137.2%19.6%45.4%13.0%13.8%0.9%0.0%
201030,8766.9%24.2%46.5%11.5%10.4%0.5%0.0%
201132,1467.1%24.6%47.1%10.8%9.8%0.5%0.0%
201234,5367.4%22.4%45.6%11.5%12.2%0.9%0.0%
201335,7956.9%22.4%45.4%11.7%12.6%0.9%0.0%
201435,5107.8%20.4%45.7%11.7%13.2%1.2%0.1%
201539,0557.4%19.5%43.6%11.8%15.5%2.0%0.2%
201639,8606.9%20.1%45.9%11.5%14.0%1.4%0.1%
201740,1687.4%17.9%45.7%12.3%15.2%1.4%0.1%
201839,2678.3%16.1%42.2%12.5%18.2%2.5%0.3%
201939,4319.1%16.1%41.9%12.4%18.0%2.3%0.2%
202030,6658.9%16.2%47.0%11.1%14.7%1.7%0.2%
202131,56310.5%12.4%42.5%11.2%19.2%3.4%0.8%
202233,24712.5%11.9%38.9%11.5%20.2%4.2%0.8%
202335,04613.4%11.1%37.7%10.3%19.8%5.8%1.8%
202434,49112.5%8.6%31.7%10.6%24.5%8.5%3.6%
202537,38110.9%9.2%31.7%11.3%25.4%8.2%3.3%
202626,7179.3%9.3%33.2%11.6%24.8%8.5%3.2%
The Average Call Waits 94 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 94 minutes in 2026, more than double what it was in 2016. 37% of calls took more than an hour to get a response in 2026, compared with 16% 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.