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

Gun Shots

Gun Shots calls over time: volume, outcomes, and response speed

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

Swipe sideways to see the full chart →
04008002009: 173 gun shots calls logged in CAD2010: 171 gun shots calls logged in CAD2011: 185 gun shots calls logged in CAD2012: 225 gun shots calls logged in CAD2013: 141 gun shots calls logged in CAD2014: 209 gun shots calls logged in CAD2015: 255 gun shots calls logged in CAD2016: 223 gun shots calls logged in CAD2017: 236 gun shots calls logged in CAD2018: 187 gun shots calls logged in CAD2019: 226 gun shots calls logged in CAD2020: 237 gun shots calls logged in CAD2021: 331 gun shots calls logged in CAD2022: 408 gun shots calls logged in CAD2023: 562 gun shots calls logged in CAD2024: 599 gun shots calls logged in CAD2025: 601 gun shots calls logged in CAD2026: 311 gun shots calls logged in CAD2009n=1732011n=1852013n=1412015n=2552017n=2362019n=2262021n=3312023n=5622025n=6012026n=311
gun shots calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodGun Shots calls logged in CAD
2009173
2010171
2011185
2012225
2013141
2014209
2015255
2016223
2017236
2018187
2019226
2020237
2021331
2022408
2023562
2024599
2025601
2026311
Calls for Gun Shots Are at Their Highest in YearsSeattle Police logged 601 gun shots calls in 2025, the most calls in any full year on record.

Gun Shots: 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: 1.7%2009 · Report taken, no arrest: 20.2%2009 · Resolved on scene: 47.4%2009 · Unable to locate: 12.1%2009 · Other (unfounded / cancelled): 18.5%2010 · Arrest / citation: 1.2%2010 · Report taken, no arrest: 35.1%2010 · Resolved on scene: 29.2%2010 · Unable to locate: 11.1%2010 · Other (unfounded / cancelled): 23.4%2011 · Arrest / citation: 4.3%2011 · Report taken, no arrest: 33.0%2011 · Resolved on scene: 30.3%2011 · Unable to locate: 7.0%2011 · Other (unfounded / cancelled): 25.4%2012 · Arrest / citation: 3.1%2012 · Report taken, no arrest: 32.4%2012 · Resolved on scene: 28.0%2012 · Unable to locate: 12.4%2012 · Other (unfounded / cancelled): 24.0%2013 · Arrest / citation: 0.7%2013 · Report taken, no arrest: 39.0%2013 · Resolved on scene: 14.2%2013 · Unable to locate: 13.5%2013 · Other (unfounded / cancelled): 32.6%2014 · Arrest / citation: 1.9%2014 · Report taken, no arrest: 40.7%2014 · Resolved on scene: 14.4%2014 · Unable to locate: 8.1%2014 · Other (unfounded / cancelled): 34.9%2015 · Arrest / citation: 1.6%2015 · Report taken, no arrest: 39.2%2015 · Resolved on scene: 27.1%2015 · Unable to locate: 5.1%2015 · Other (unfounded / cancelled): 27.1%2016 · Arrest / citation: 3.1%2016 · Report taken, no arrest: 35.4%2016 · Resolved on scene: 22.9%2016 · Unable to locate: 9.9%2016 · Other (unfounded / cancelled): 28.7%2017 · Arrest / citation: 2.1%2017 · Report taken, no arrest: 43.6%2017 · Resolved on scene: 14.8%2017 · Unable to locate: 11.9%2017 · Other (unfounded / cancelled): 27.5%2018 · Arrest / citation: 1.1%2018 · Report taken, no arrest: 40.6%2018 · Resolved on scene: 10.7%2018 · Unable to locate: 16.0%2018 · Other (unfounded / cancelled): 31.6%2019 · Arrest / citation: 1.8%2019 · Report taken, no arrest: 43.4%2019 · Resolved on scene: 15.0%2019 · Unable to locate: 16.8%2019 · Other (unfounded / cancelled): 23.0%2020 · Arrest / citation: 0.8%2020 · Report taken, no arrest: 39.2%2020 · Resolved on scene: 11.8%2020 · Unable to locate: 22.4%2020 · Other (unfounded / cancelled): 25.7%2021 · Arrest / citation: 0.9%2021 · Report taken, no arrest: 46.2%2021 · Resolved on scene: 10.6%2021 · Unable to locate: 15.4%2021 · Other (unfounded / cancelled): 26.9%2022 · Arrest / citation: 1.5%2022 · Report taken, no arrest: 37.3%2022 · Resolved on scene: 11.5%2022 · Unable to locate: 27.7%2022 · Other (unfounded / cancelled): 22.1%2023 · Arrest / citation: 0.2%2023 · Report taken, no arrest: 40.9%2023 · Resolved on scene: 11.2%2023 · Unable to locate: 27.9%2023 · Other (unfounded / cancelled): 19.8%2024 · Arrest / citation: 0.5%2024 · Report taken, no arrest: 37.1%2024 · Resolved on scene: 9.3%2024 · Unable to locate: 34.9%2024 · Other (unfounded / cancelled): 18.2%2025 · Arrest / citation: 1.0%2025 · Report taken, no arrest: 38.6%2025 · Resolved on scene: 5.8%2025 · Unable to locate: 37.8%2025 · Other (unfounded / cancelled): 16.8%2026 · Arrest / citation: 1.3%2026 · Report taken, no arrest: 39.5%2026 · Resolved on scene: 5.8%2026 · Unable to locate: 35.7%2026 · Other (unfounded / cancelled): 17.7%2009n=1732011n=1852013n=1412015n=2552017n=2362019n=2262021n=3312023n=5622025n=6012026n=311
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)
20091731.7%20.2%47.4%12.1%18.5%
20101711.2%35.1%29.2%11.1%23.4%
20111854.3%33.0%30.3%7.0%25.4%
20122253.1%32.4%28.0%12.4%24.0%
20131410.7%39.0%14.2%13.5%32.6%
20142091.9%40.7%14.4%8.1%34.9%
20152551.6%39.2%27.1%5.1%27.1%
20162233.1%35.4%22.9%9.9%28.7%
20172362.1%43.6%14.8%11.9%27.5%
20181871.1%40.6%10.7%16.0%31.6%
20192261.8%43.4%15.0%16.8%23.0%
20202370.8%39.2%11.8%22.4%25.7%
20213310.9%46.2%10.6%15.4%26.9%
20224081.5%37.3%11.5%27.7%22.1%
20235620.2%40.9%11.2%27.9%19.8%
20245990.5%37.1%9.3%34.9%18.2%
20256011.0%38.6%5.8%37.8%16.8%
20263111.3%39.5%5.8%35.7%17.7%
36% of Calls for Gun Shots End “Unable to Locate,” Up From 10%Report-taken outcomes moved from 35% of calls in 2016 to 40% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Gun Shots: 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 12% of gun shots 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 min12 min25 min2009: 6.6 min2010: 5.2 min2011: 5.0 min2012: 3.7 min2013: 1.4 min2014: 8.5 min2015: 4.8 min2016: 3.0 min2017: 8.4 min2018: 6.3 min2019: 7.3 min2020: 5.7 min2021: 3.2 min2022: 4.8 min2023: 8.1 min2024: 10.3 min2025: 10.1 min2026: 12.2 min2009: 9.9 min2010: 9.4 min2011: 10.0 min2012: 9.3 min2013: 6.5 min2014: 14.6 min2015: 9.0 min2016: 9.4 min2017: 16.0 min2018: 13.2 min2019: 10.8 min2020: 13.3 min2021: 9.7 min2022: 11.1 min2023: 15.2 min2024: 16.2 min2025: 19.5 min2026: 18.1 min2009n=1432011n=1542013n=1192015n=2162017n=2002019n=1942021n=2882023n=5152025n=5402026n=285
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
20091436.6 min9.9 min
20101405.2 min9.4 min
20111545.0 min10.0 min
20121903.7 min9.3 min
20131191.4 min6.5 min
20141778.5 min14.6 min
20152164.8 min9.0 min
20161943.0 min9.4 min
20172008.4 min16.0 min
20181646.3 min13.2 min
20191947.3 min10.8 min
20202075.7 min13.3 min
20212883.2 min9.7 min
20223704.8 min11.1 min
20235158.1 min15.2 min
202454310.3 min16.2 min
202554010.1 min19.5 min
202628512.2 min18.1 min
The Average Call Waits 18 Minutes for an Officer to ArriveAs calls rose 170% between 2016 and 2025, average response time has increased 93% in the past 10 years, from 9.4 minutes in 2016 to 18 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.

Gun Shots: 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 12% of gun shots 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: 10.5%2009 · 0–5 min: 56.6%2009 · 5–30 min: 27.3%2009 · 30–60 min: 1.4%2009 · 1–4 hr: 4.2%2010 · No recorded response: 14.3%2010 · 0–5 min: 53.6%2010 · 5–30 min: 26.4%2010 · 30–60 min: 2.9%2010 · 1–4 hr: 2.9%2011 · No recorded response: 15.6%2011 · 0–5 min: 44.2%2011 · 5–30 min: 35.1%2011 · 30–60 min: 3.2%2011 · 1–4 hr: 2.0%2012 · No recorded response: 13.2%2012 · 0–5 min: 47.4%2012 · 5–30 min: 33.2%2012 · 30–60 min: 4.2%2012 · 1–4 hr: 2.1%2013 · No recorded response: 16.0%2013 · 0–5 min: 48.7%2013 · 5–30 min: 32.8%2013 · 30–60 min: 1.7%2013 · 1–4 hr: 0.8%2014 · No recorded response: 16.9%2014 · 0–5 min: 53.1%2014 · 5–30 min: 24.3%2014 · 30–60 min: 2.3%2014 · 1–4 hr: 2.8%2014 · Over 8 hr: 0.6%2015 · No recorded response: 13.9%2015 · 0–5 min: 50.5%2015 · 5–30 min: 28.7%2015 · 30–60 min: 4.6%2015 · 1–4 hr: 2.3%2016 · No recorded response: 15.5%2016 · 0–5 min: 40.7%2016 · 5–30 min: 39.7%2016 · 30–60 min: 2.1%2016 · 1–4 hr: 2.1%2017 · No recorded response: 15.0%2017 · 0–5 min: 42.5%2017 · 5–30 min: 35.0%2017 · 30–60 min: 3.0%2017 · 1–4 hr: 4.0%2017 · Over 8 hr: 0.5%2018 · No recorded response: 14.0%2018 · 0–5 min: 43.9%2018 · 5–30 min: 33.5%2018 · 30–60 min: 5.5%2018 · 1–4 hr: 3.0%2019 · No recorded response: 10.3%2019 · 0–5 min: 44.3%2019 · 5–30 min: 41.8%2019 · 30–60 min: 1.6%2019 · 1–4 hr: 1.6%2019 · 4–8 hr: 0.5%2020 · No recorded response: 13.0%2020 · 0–5 min: 38.6%2020 · 5–30 min: 41.1%2020 · 30–60 min: 3.4%2020 · 1–4 hr: 3.9%2021 · No recorded response: 14.2%2021 · 0–5 min: 40.6%2021 · 5–30 min: 40.6%2021 · 30–60 min: 1.7%2021 · 1–4 hr: 2.8%2022 · No recorded response: 16.5%2022 · 0–5 min: 35.4%2022 · 5–30 min: 44.6%2022 · 30–60 min: 1.9%2022 · 1–4 hr: 1.1%2022 · 4–8 hr: 0.5%2023 · No recorded response: 11.8%2023 · 0–5 min: 34.4%2023 · 5–30 min: 49.5%2023 · 30–60 min: 1.8%2023 · 1–4 hr: 1.4%2023 · 4–8 hr: 1.0%2023 · Over 8 hr: 0.2%2024 · No recorded response: 10.7%2024 · 0–5 min: 35.7%2024 · 5–30 min: 47.5%2024 · 30–60 min: 2.8%2024 · 1–4 hr: 2.0%2024 · 4–8 hr: 1.1%2024 · Over 8 hr: 0.2%2025 · No recorded response: 13.7%2025 · 0–5 min: 36.1%2025 · 5–30 min: 43.7%2025 · 30–60 min: 2.2%2025 · 1–4 hr: 2.6%2025 · 4–8 hr: 1.1%2025 · Over 8 hr: 0.6%2026 · No recorded response: 12.6%2026 · 0–5 min: 34.0%2026 · 5–30 min: 47.7%2026 · 30–60 min: 1.8%2026 · 1–4 hr: 2.8%2026 · 4–8 hr: 0.7%2026 · Over 8 hr: 0.3%2009n=1432011n=1542013n=1192015n=2162017n=2002019n=1942021n=2882023n=5152025n=5402026n=285
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 hrOver 8 hr4–8 hr
200914310.5%56.6%27.3%1.4%4.2%——
201014014.3%53.6%26.4%2.9%2.9%——
201115415.6%44.2%35.1%3.2%2.0%——
201219013.2%47.4%33.2%4.2%2.1%——
201311916.0%48.7%32.8%1.7%0.8%——
201417716.9%53.1%24.3%2.3%2.8%0.6%—
201521613.9%50.5%28.7%4.6%2.3%——
201619415.5%40.7%39.7%2.1%2.1%——
201720015.0%42.5%35.0%3.0%4.0%0.5%—
201816414.0%43.9%33.5%5.5%3.0%——
201919410.3%44.3%41.8%1.6%1.6%—0.5%
202020713.0%38.6%41.1%3.4%3.9%——
202128814.2%40.6%40.6%1.7%2.8%——
202237016.5%35.4%44.6%1.9%1.1%—0.5%
202351511.8%34.4%49.5%1.8%1.4%0.2%1.0%
202454310.7%35.7%47.5%2.8%2.0%0.2%1.1%
202554013.7%36.1%43.7%2.2%2.6%0.6%1.1%
202628512.6%34.0%47.7%1.8%2.8%0.3%0.7%
The Average Call Waits 12 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 12 minutes in 2026, more than double what it was in 2016. 4% of calls took more than an hour to get a response in 2026, compared with 2% 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.