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

Assaults

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

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

Swipe sideways to see the full chart →
015,00030,0002009: 4,764 assaults calls logged in CAD2010: 8,390 assaults calls logged in CAD2011: 8,196 assaults calls logged in CAD2012: 8,366 assaults calls logged in CAD2013: 8,925 assaults calls logged in CAD2014: 25,511 assaults calls logged in CAD2015: 24,713 assaults calls logged in CAD2016: 24,819 assaults calls logged in CAD2017: 24,638 assaults calls logged in CAD2018: 26,134 assaults calls logged in CAD2019: 20,531 assaults calls logged in CAD2020: 14,021 assaults calls logged in CAD2021: 13,653 assaults calls logged in CAD2022: 12,926 assaults calls logged in CAD2023: 13,153 assaults calls logged in CAD2024: 12,202 assaults calls logged in CAD2025: 11,880 assaults calls logged in CAD2026: 8,117 assaults calls logged in CAD2009n=4,7642011n=8,1962013n=8,9252015n=24,7132017n=24,6382019n=20,5312021n=13,6532023n=13,1532025n=11,8802026n=8,117
assaults calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodAssaults calls logged in CAD
20094,764
20108,390
20118,196
20128,366
20138,925
201425,511
201524,713
201624,819
201724,638
201826,134
201920,531
202014,021
202113,653
202212,926
202313,153
202412,202
202511,880
20268,117
Calls for Assaults Are Down 55% From Their 2018 PeakSeattle Police logged 26,134 assaults calls in 2018 and 11,880 in 2025, the most recent full year.

Assaults: 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: 16.0%2009 · Report taken, no arrest: 59.2%2009 · Resolved on scene: 14.4%2009 · Unable to locate: 7.5%2009 · Other (unfounded / cancelled): 2.9%2010 · Arrest / citation: 17.8%2010 · Report taken, no arrest: 62.5%2010 · Resolved on scene: 11.7%2010 · Unable to locate: 5.6%2010 · Other (unfounded / cancelled): 2.4%2011 · Arrest / citation: 17.5%2011 · Report taken, no arrest: 63.4%2011 · Resolved on scene: 10.8%2011 · Unable to locate: 6.0%2011 · Other (unfounded / cancelled): 2.4%2012 · Arrest / citation: 16.7%2012 · Report taken, no arrest: 62.8%2012 · Resolved on scene: 11.6%2012 · Unable to locate: 6.1%2012 · Other (unfounded / cancelled): 2.8%2013 · Arrest / citation: 14.4%2013 · Report taken, no arrest: 61.9%2013 · Resolved on scene: 15.6%2013 · Unable to locate: 6.0%2013 · Other (unfounded / cancelled): 2.1%2014 · Arrest / citation: 5.0%2014 · Report taken, no arrest: 22.7%2014 · Resolved on scene: 68.9%2014 · Unable to locate: 2.5%2014 · Other (unfounded / cancelled): 0.8%2015 · Arrest / citation: 6.0%2015 · Report taken, no arrest: 24.5%2015 · Resolved on scene: 65.7%2015 · Unable to locate: 2.8%2015 · Other (unfounded / cancelled): 0.9%2016 · Arrest / citation: 6.2%2016 · Report taken, no arrest: 24.0%2016 · Resolved on scene: 66.0%2016 · Unable to locate: 2.8%2016 · Other (unfounded / cancelled): 1.0%2017 · Arrest / citation: 7.0%2017 · Report taken, no arrest: 24.5%2017 · Resolved on scene: 64.9%2017 · Unable to locate: 2.7%2017 · Other (unfounded / cancelled): 1.1%2018 · Arrest / citation: 7.3%2018 · Report taken, no arrest: 26.4%2018 · Resolved on scene: 62.6%2018 · Unable to locate: 2.9%2018 · Other (unfounded / cancelled): 0.8%2019 · Arrest / citation: 9.4%2019 · Report taken, no arrest: 31.8%2019 · Resolved on scene: 53.6%2019 · Unable to locate: 4.0%2019 · Other (unfounded / cancelled): 1.1%2020 · Arrest / citation: 11.6%2020 · Report taken, no arrest: 42.0%2020 · Resolved on scene: 39.2%2020 · Unable to locate: 5.6%2020 · Other (unfounded / cancelled): 1.5%2021 · Arrest / citation: 12.5%2021 · Report taken, no arrest: 48.2%2021 · Resolved on scene: 30.2%2021 · Unable to locate: 7.8%2021 · Other (unfounded / cancelled): 1.5%2022 · Arrest / citation: 13.8%2022 · Report taken, no arrest: 51.8%2022 · Resolved on scene: 23.5%2022 · Unable to locate: 9.4%2022 · Other (unfounded / cancelled): 1.3%2023 · Arrest / citation: 13.0%2023 · Report taken, no arrest: 49.8%2023 · Resolved on scene: 24.8%2023 · Unable to locate: 10.9%2023 · Other (unfounded / cancelled): 1.5%2024 · Arrest / citation: 13.5%2024 · Report taken, no arrest: 49.3%2024 · Resolved on scene: 21.6%2024 · Unable to locate: 14.2%2024 · Other (unfounded / cancelled): 1.5%2025 · Arrest / citation: 14.6%2025 · Report taken, no arrest: 47.4%2025 · Resolved on scene: 19.4%2025 · Unable to locate: 16.0%2025 · Other (unfounded / cancelled): 2.6%2026 · Arrest / citation: 16.2%2026 · Report taken, no arrest: 49.0%2026 · Resolved on scene: 16.0%2026 · Unable to locate: 16.4%2026 · Other (unfounded / cancelled): 2.5%2009n=4,7642011n=8,1962013n=8,9252015n=24,7132017n=24,6382019n=20,5312021n=13,6532023n=13,1532025n=11,8802026n=8,117
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)
20094,76416.0%59.2%14.4%7.5%2.9%
20108,39017.8%62.5%11.7%5.6%2.4%
20118,19617.5%63.4%10.8%6.0%2.4%
20128,36616.7%62.8%11.6%6.1%2.8%
20138,92514.4%61.9%15.6%6.0%2.1%
201425,5115.0%22.7%68.9%2.5%0.8%
201524,7136.0%24.5%65.7%2.8%0.9%
201624,8196.2%24.0%66.0%2.8%1.0%
201724,6387.0%24.5%64.9%2.7%1.1%
201826,1347.3%26.4%62.6%2.9%0.8%
201920,5319.4%31.8%53.6%4.0%1.1%
202014,02111.6%42.0%39.2%5.6%1.5%
202113,65312.5%48.2%30.2%7.8%1.5%
202212,92613.8%51.8%23.5%9.4%1.3%
202313,15313.0%49.8%24.8%10.9%1.5%
202412,20213.5%49.3%21.6%14.2%1.5%
202511,88014.6%47.4%19.4%16.0%2.6%
20268,11716.2%49.0%16.0%16.4%2.5%
16% of Calls for Assaults End “Unable to Locate,” Up From 3%Report-taken outcomes moved from 24% of calls in 2016 to 49% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Assaults: 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 47% of assaults 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: 25.8 min2010: 21.1 min2011: 21.3 min2012: 26.1 min2013: 27.0 min2014: 29.5 min2015: 31.2 min2016: 29.0 min2017: 30.3 min2018: 40.2 min2019: 39.2 min2020: 38.3 min2021: 54.0 min2022: 57.1 min2023: 65.1 min2024: 102.5 min2025: 105.6 min2026: 97.0 min2009: 33.7 min2010: 28.5 min2011: 29.3 min2012: 34.5 min2013: 35.4 min2014: 38.1 min2015: 38.3 min2016: 36.5 min2017: 39.0 min2018: 48.7 min2019: 47.7 min2020: 45.7 min2021: 62.1 min2022: 64.1 min2023: 71.1 min2024: 110.8 min2025: 115.9 min2026: 105.3 min2009n=4,0712011n=6,8432013n=7,3332015n=7,9742017n=8,1112019n=8,8432021n=9,3312023n=9,6682025n=9,2532026n=6,544
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
20094,07125.8 min33.7 min
20107,05321.1 min28.5 min
20116,84321.3 min29.3 min
20127,02726.1 min34.5 min
20137,33327.0 min35.4 min
20147,69629.5 min38.1 min
20157,97431.2 min38.3 min
20168,11329.0 min36.5 min
20178,11130.3 min39.0 min
20189,07140.2 min48.7 min
20198,84339.2 min47.7 min
20208,30538.3 min45.7 min
20219,33154.0 min62.1 min
20229,58857.1 min64.1 min
20239,66865.1 min71.1 min
20249,261102.5 min110.8 min
20259,253105.6 min115.9 min
20266,54497.0 min105.3 min
The Average Call Waits 105 Minutes for an Officer to ArriveDespite a 52% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 36 minutes in 2016 to 105 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.

Assaults: 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 47% of assaults 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: 2.9%2009 · 0–5 min: 26.5%2009 · 5–30 min: 42.1%2009 · 30–60 min: 11.2%2009 · 1–4 hr: 16.0%2009 · 4–8 hr: 1.1%2009 · Over 8 hr: 0.1%2010 · No recorded response: 3.1%2010 · 0–5 min: 28.6%2010 · 5–30 min: 42.5%2010 · 30–60 min: 12.1%2010 · 1–4 hr: 13.0%2010 · 4–8 hr: 0.6%2010 · Over 8 hr: 0.1%2011 · No recorded response: 3.1%2011 · 0–5 min: 28.4%2011 · 5–30 min: 43.5%2011 · 30–60 min: 11.0%2011 · 1–4 hr: 13.0%2011 · 4–8 hr: 0.8%2011 · Over 8 hr: 0.1%2012 · No recorded response: 2.7%2012 · 0–5 min: 25.3%2012 · 5–30 min: 43.3%2012 · 30–60 min: 12.0%2012 · 1–4 hr: 15.2%2012 · 4–8 hr: 1.4%2012 · Over 8 hr: 0.1%2013 · No recorded response: 2.8%2013 · 0–5 min: 27.2%2013 · 5–30 min: 41.3%2013 · 30–60 min: 11.4%2013 · 1–4 hr: 15.6%2013 · 4–8 hr: 1.5%2013 · Over 8 hr: 0.2%2014 · No recorded response: 3.1%2014 · 0–5 min: 26.0%2014 · 5–30 min: 42.8%2014 · 30–60 min: 10.2%2014 · 1–4 hr: 15.6%2014 · 4–8 hr: 2.2%2014 · Over 8 hr: 0.2%2015 · No recorded response: 2.9%2015 · 0–5 min: 27.7%2015 · 5–30 min: 42.4%2015 · 30–60 min: 10.0%2015 · 1–4 hr: 14.5%2015 · 4–8 hr: 2.2%2015 · Over 8 hr: 0.4%2016 · No recorded response: 3.2%2016 · 0–5 min: 29.2%2016 · 5–30 min: 42.6%2016 · 30–60 min: 8.8%2016 · 1–4 hr: 13.5%2016 · 4–8 hr: 2.4%2016 · Over 8 hr: 0.3%2017 · No recorded response: 3.4%2017 · 0–5 min: 25.9%2017 · 5–30 min: 42.9%2017 · 30–60 min: 9.9%2017 · 1–4 hr: 15.3%2017 · 4–8 hr: 2.5%2017 · Over 8 hr: 0.2%2018 · No recorded response: 3.2%2018 · 0–5 min: 23.5%2018 · 5–30 min: 40.8%2018 · 30–60 min: 9.9%2018 · 1–4 hr: 18.6%2018 · 4–8 hr: 3.5%2018 · Over 8 hr: 0.5%2019 · No recorded response: 3.4%2019 · 0–5 min: 24.4%2019 · 5–30 min: 40.4%2019 · 30–60 min: 10.2%2019 · 1–4 hr: 17.7%2019 · 4–8 hr: 3.5%2019 · Over 8 hr: 0.5%2020 · No recorded response: 3.5%2020 · 0–5 min: 23.2%2020 · 5–30 min: 43.0%2020 · 30–60 min: 9.7%2020 · 1–4 hr: 17.1%2020 · 4–8 hr: 3.1%2020 · Over 8 hr: 0.5%2021 · No recorded response: 4.3%2021 · 0–5 min: 19.3%2021 · 5–30 min: 42.5%2021 · 30–60 min: 8.9%2021 · 1–4 hr: 18.9%2021 · 4–8 hr: 4.5%2021 · Over 8 hr: 1.5%2022 · No recorded response: 4.1%2022 · 0–5 min: 21.8%2022 · 5–30 min: 40.8%2022 · 30–60 min: 9.2%2022 · 1–4 hr: 17.4%2022 · 4–8 hr: 4.7%2022 · Over 8 hr: 2.0%2023 · No recorded response: 5.4%2023 · 0–5 min: 21.4%2023 · 5–30 min: 41.7%2023 · 30–60 min: 7.7%2023 · 1–4 hr: 15.6%2023 · 4–8 hr: 5.5%2023 · Over 8 hr: 2.7%2024 · No recorded response: 6.1%2024 · 0–5 min: 15.9%2024 · 5–30 min: 35.1%2024 · 30–60 min: 8.9%2024 · 1–4 hr: 20.5%2024 · 4–8 hr: 8.4%2024 · Over 8 hr: 5.0%2025 · No recorded response: 3.8%2025 · 0–5 min: 15.4%2025 · 5–30 min: 33.9%2025 · 30–60 min: 9.9%2025 · 1–4 hr: 22.3%2025 · 4–8 hr: 9.7%2025 · Over 8 hr: 5.0%2026 · No recorded response: 3.1%2026 · 0–5 min: 16.6%2026 · 5–30 min: 34.7%2026 · 30–60 min: 9.9%2026 · 1–4 hr: 22.4%2026 · 4–8 hr: 9.0%2026 · Over 8 hr: 4.3%2009n=4,0712011n=6,8432013n=7,3332015n=7,9742017n=8,1112019n=8,8432021n=9,3312023n=9,6682025n=9,2532026n=6,544
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
20094,0712.9%26.5%42.1%11.2%16.0%1.1%0.1%
20107,0533.1%28.6%42.5%12.1%13.0%0.6%0.1%
20116,8433.1%28.4%43.5%11.0%13.0%0.8%0.1%
20127,0272.7%25.3%43.3%12.0%15.2%1.4%0.1%
20137,3332.8%27.2%41.3%11.4%15.6%1.5%0.2%
20147,6963.1%26.0%42.8%10.2%15.6%2.2%0.2%
20157,9742.9%27.7%42.4%10.0%14.5%2.2%0.4%
20168,1133.2%29.2%42.6%8.8%13.5%2.4%0.3%
20178,1113.4%25.9%42.9%9.9%15.3%2.5%0.2%
20189,0713.2%23.5%40.8%9.9%18.6%3.5%0.5%
20198,8433.4%24.4%40.4%10.2%17.7%3.5%0.5%
20208,3053.5%23.2%43.0%9.7%17.1%3.1%0.5%
20219,3314.3%19.3%42.5%8.9%18.9%4.5%1.5%
20229,5884.1%21.8%40.8%9.2%17.4%4.7%2.0%
20239,6685.4%21.4%41.7%7.7%15.6%5.5%2.7%
20249,2616.1%15.9%35.1%8.9%20.5%8.4%5.0%
20259,2533.8%15.4%33.9%9.9%22.3%9.7%5.0%
20266,5443.1%16.6%34.7%9.9%22.4%9.0%4.3%
The Average Call Waits 97 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 97 minutes in 2026, more than double what it was in 2016. 36% 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.