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

Weapon, Person with

Weapon, Person with calls over time: volume, outcomes, and response speed

Weapon, Person with: 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 (30% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
06001,2002009: 485 weapon, person with calls logged in CAD2010: 747 weapon, person with calls logged in CAD2011: 742 weapon, person with calls logged in CAD2012: 706 weapon, person with calls logged in CAD2013: 709 weapon, person with calls logged in CAD2014: 743 weapon, person with calls logged in CAD2015: 899 weapon, person with calls logged in CAD2016: 825 weapon, person with calls logged in CAD2017: 898 weapon, person with calls logged in CAD2018: 932 weapon, person with calls logged in CAD2019: 886 weapon, person with calls logged in CAD2020: 754 weapon, person with calls logged in CAD2021: 742 weapon, person with calls logged in CAD2022: 959 weapon, person with calls logged in CAD2023: 945 weapon, person with calls logged in CAD2024: 1,002 weapon, person with calls logged in CAD2025: 925 weapon, person with calls logged in CAD2026: 614 weapon, person with calls logged in CAD2009n=4852011n=7422013n=7092015n=8992017n=8982019n=8862021n=7422023n=9452025n=9252026n=614
weapon, person with calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodWeapon, person with calls logged in CAD
2009485
2010747
2011742
2012706
2013709
2014743
2015899
2016825
2017898
2018932
2019886
2020754
2021742
2022959
2023945
20241,002
2025925
2026614
Calls in This Category Are Holding Near Their PeakSeattle Police logged 925 calls in this category in 2025, the most recent full year, close to the 1,002 in 2024.

Weapon, Person with: 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: 26.2%2009 · Report taken, no arrest: 29.7%2009 · Resolved on scene: 23.3%2009 · Unable to locate: 14.2%2009 · Other (unfounded / cancelled): 6.6%2010 · Arrest / citation: 30.4%2010 · Report taken, no arrest: 28.6%2010 · Resolved on scene: 25.6%2010 · Unable to locate: 11.5%2010 · Other (unfounded / cancelled): 3.9%2011 · Arrest / citation: 27.2%2011 · Report taken, no arrest: 35.7%2011 · Resolved on scene: 22.9%2011 · Unable to locate: 10.6%2011 · Other (unfounded / cancelled): 3.5%2012 · Arrest / citation: 22.5%2012 · Report taken, no arrest: 36.5%2012 · Resolved on scene: 25.9%2012 · Unable to locate: 12.5%2012 · Other (unfounded / cancelled): 2.5%2013 · Arrest / citation: 20.3%2013 · Report taken, no arrest: 37.0%2013 · Resolved on scene: 27.1%2013 · Unable to locate: 12.6%2013 · Other (unfounded / cancelled): 3.1%2014 · Arrest / citation: 17.6%2014 · Report taken, no arrest: 42.5%2014 · Resolved on scene: 22.1%2014 · Unable to locate: 15.5%2014 · Other (unfounded / cancelled): 2.3%2015 · Arrest / citation: 16.9%2015 · Report taken, no arrest: 44.6%2015 · Resolved on scene: 19.0%2015 · Unable to locate: 17.0%2015 · Other (unfounded / cancelled): 2.5%2016 · Arrest / citation: 18.7%2016 · Report taken, no arrest: 40.1%2016 · Resolved on scene: 19.6%2016 · Unable to locate: 17.9%2016 · Other (unfounded / cancelled): 3.7%2017 · Arrest / citation: 18.0%2017 · Report taken, no arrest: 43.9%2017 · Resolved on scene: 17.9%2017 · Unable to locate: 17.3%2017 · Other (unfounded / cancelled): 2.9%2018 · Arrest / citation: 18.6%2018 · Report taken, no arrest: 45.0%2018 · Resolved on scene: 17.6%2018 · Unable to locate: 15.2%2018 · Other (unfounded / cancelled): 3.7%2019 · Arrest / citation: 20.9%2019 · Report taken, no arrest: 44.4%2019 · Resolved on scene: 16.0%2019 · Unable to locate: 16.1%2019 · Other (unfounded / cancelled): 2.6%2020 · Arrest / citation: 20.7%2020 · Report taken, no arrest: 41.1%2020 · Resolved on scene: 15.9%2020 · Unable to locate: 18.7%2020 · Other (unfounded / cancelled): 3.6%2021 · Arrest / citation: 16.8%2021 · Report taken, no arrest: 37.9%2021 · Resolved on scene: 18.7%2021 · Unable to locate: 23.6%2021 · Other (unfounded / cancelled): 3.0%2022 · Arrest / citation: 17.7%2022 · Report taken, no arrest: 42.3%2022 · Resolved on scene: 16.8%2022 · Unable to locate: 20.6%2022 · Other (unfounded / cancelled): 2.5%2023 · Arrest / citation: 19.9%2023 · Report taken, no arrest: 38.4%2023 · Resolved on scene: 15.7%2023 · Unable to locate: 23.9%2023 · Other (unfounded / cancelled): 2.1%2024 · Arrest / citation: 21.9%2024 · Report taken, no arrest: 36.7%2024 · Resolved on scene: 20.6%2024 · Unable to locate: 17.9%2024 · Other (unfounded / cancelled): 3.0%2025 · Arrest / citation: 22.4%2025 · Report taken, no arrest: 37.5%2025 · Resolved on scene: 18.7%2025 · Unable to locate: 19.7%2025 · Other (unfounded / cancelled): 1.7%2026 · Arrest / citation: 22.8%2026 · Report taken, no arrest: 39.6%2026 · Resolved on scene: 13.8%2026 · Unable to locate: 21.8%2026 · Other (unfounded / cancelled): 2.0%2009n=4852011n=7422013n=7092015n=8992017n=8982019n=8862021n=7422023n=9452025n=9252026n=614
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)
200948526.2%29.7%23.3%14.2%6.6%
201074730.4%28.6%25.6%11.5%3.9%
201174227.2%35.7%22.9%10.6%3.5%
201270622.5%36.5%25.9%12.5%2.5%
201370920.3%37.0%27.1%12.6%3.1%
201474317.6%42.5%22.1%15.5%2.3%
201589916.9%44.6%19.0%17.0%2.5%
201682518.7%40.1%19.6%17.9%3.7%
201789818.0%43.9%17.9%17.3%2.9%
201893218.6%45.0%17.6%15.2%3.7%
201988620.9%44.4%16.0%16.1%2.6%
202075420.7%41.1%15.9%18.7%3.6%
202174216.8%37.9%18.7%23.6%3.0%
202295917.7%42.3%16.8%20.6%2.5%
202394519.9%38.4%15.7%23.9%2.1%
20241,00221.9%36.7%20.6%17.9%3.0%
202592522.4%37.5%18.7%19.7%1.7%
202661422.8%39.6%13.8%21.8%2.0%
22% of Calls in This Category End “Unable to Locate,” Up From 18%Report-taken outcomes were 40% of calls in both 2016 and 2026. “Unable to locate” means officers could not find the incident or the person who called.

Weapon, Person with: 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 30% of events in this category, 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 min25 min50 min2009: 7.3 min2010: 3.9 min2011: 7.6 min2012: 6.7 min2013: 6.2 min2014: 7.9 min2015: 7.5 min2016: 6.3 min2017: 6.1 min2018: 10.4 min2019: 9.7 min2020: 8.8 min2021: 11.6 min2022: 15.0 min2023: 20.4 min2024: 26.3 min2025: 35.1 min2026: 26.8 min2009: 11.1 min2010: 7.8 min2011: 11.5 min2012: 11.8 min2013: 10.2 min2014: 12.0 min2015: 12.2 min2016: 10.5 min2017: 12.0 min2018: 17.0 min2019: 15.2 min2020: 15.3 min2021: 18.9 min2022: 19.9 min2023: 27.0 min2024: 31.7 min2025: 41.7 min2026: 33.0 min2009n=3332011n=4932013n=5062015n=6332017n=6402019n=5902021n=5952023n=6952025n=6112026n=417
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
20093337.3 min11.1 min
20104743.9 min7.8 min
20114937.6 min11.5 min
20124816.7 min11.8 min
20135066.2 min10.2 min
20145167.9 min12.0 min
20156337.5 min12.2 min
20166156.3 min10.5 min
20176406.1 min12.0 min
201865810.4 min17.0 min
20195909.7 min15.2 min
20205328.8 min15.3 min
202159511.6 min18.9 min
202269015.0 min19.9 min
202369520.4 min27.0 min
202464026.3 min31.7 min
202561135.1 min41.7 min
202641726.8 min33.0 min
The Average Call Waits 33 Minutes for an Officer to ArriveAs calls rose 12% between 2016 and 2025, average response time has grown about 3-fold in the past 10 years, from 10 minutes in 2016 to 33 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.

Weapon, Person with: 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 30% of events in this category, 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: 1.8%2009 · 0–5 min: 60.7%2009 · 5–30 min: 30.3%2009 · 30–60 min: 3.3%2009 · 1–4 hr: 3.6%2009 · 4–8 hr: 0.3%2010 · No recorded response: 1.9%2010 · 0–5 min: 62.2%2010 · 5–30 min: 31.6%2010 · 30–60 min: 3.2%2010 · 1–4 hr: 1.1%2011 · No recorded response: 2.8%2011 · 0–5 min: 62.5%2011 · 5–30 min: 28.0%2011 · 30–60 min: 3.5%2011 · 1–4 hr: 2.4%2011 · 4–8 hr: 0.6%2011 · Over 8 hr: 0.2%2012 · No recorded response: 2.1%2012 · 0–5 min: 59.5%2012 · 5–30 min: 30.4%2012 · 30–60 min: 4.2%2012 · 1–4 hr: 3.8%2012 · 4–8 hr: 0.2%2013 · No recorded response: 2.6%2013 · 0–5 min: 58.7%2013 · 5–30 min: 33.4%2013 · 30–60 min: 2.2%2013 · 1–4 hr: 3.0%2013 · 4–8 hr: 0.2%2014 · No recorded response: 3.3%2014 · 0–5 min: 53.7%2014 · 5–30 min: 35.3%2014 · 30–60 min: 3.5%2014 · 1–4 hr: 4.1%2014 · 4–8 hr: 0.2%2015 · No recorded response: 2.8%2015 · 0–5 min: 54.3%2015 · 5–30 min: 36.0%2015 · 30–60 min: 3.2%2015 · 1–4 hr: 3.0%2015 · 4–8 hr: 0.6%2016 · No recorded response: 3.1%2016 · 0–5 min: 50.1%2016 · 5–30 min: 40.2%2016 · 30–60 min: 3.6%2016 · 1–4 hr: 3.1%2017 · No recorded response: 3.4%2017 · 0–5 min: 45.6%2017 · 5–30 min: 45.2%2017 · 30–60 min: 2.2%2017 · 1–4 hr: 3.3%2017 · 4–8 hr: 0.3%2018 · No recorded response: 4.1%2018 · 0–5 min: 42.7%2018 · 5–30 min: 42.4%2018 · 30–60 min: 5.0%2018 · 1–4 hr: 5.2%2018 · 4–8 hr: 0.6%2019 · No recorded response: 4.6%2019 · 0–5 min: 43.9%2019 · 5–30 min: 42.9%2019 · 30–60 min: 2.9%2019 · 1–4 hr: 5.1%2019 · 4–8 hr: 0.7%2020 · No recorded response: 6.0%2020 · 0–5 min: 39.7%2020 · 5–30 min: 44.9%2020 · 30–60 min: 3.8%2020 · 1–4 hr: 5.1%2020 · 4–8 hr: 0.6%2021 · No recorded response: 4.7%2021 · 0–5 min: 37.1%2021 · 5–30 min: 47.2%2021 · 30–60 min: 4.5%2021 · 1–4 hr: 5.0%2021 · 4–8 hr: 1.3%2022 · No recorded response: 4.1%2022 · 0–5 min: 30.6%2022 · 5–30 min: 53.8%2022 · 30–60 min: 4.3%2022 · 1–4 hr: 6.2%2022 · 4–8 hr: 1.0%2023 · No recorded response: 4.8%2023 · 0–5 min: 32.8%2023 · 5–30 min: 49.6%2023 · 30–60 min: 4.2%2023 · 1–4 hr: 6.5%2023 · 4–8 hr: 1.6%2023 · Over 8 hr: 0.6%2024 · No recorded response: 6.4%2024 · 0–5 min: 28.9%2024 · 5–30 min: 47.3%2024 · 30–60 min: 6.1%2024 · 1–4 hr: 9.4%2024 · 4–8 hr: 0.9%2024 · Over 8 hr: 0.9%2025 · No recorded response: 4.9%2025 · 0–5 min: 26.2%2025 · 5–30 min: 44.8%2025 · 30–60 min: 7.7%2025 · 1–4 hr: 12.4%2025 · 4–8 hr: 3.1%2025 · Over 8 hr: 0.8%2026 · No recorded response: 3.8%2026 · 0–5 min: 26.9%2026 · 5–30 min: 50.1%2026 · 30–60 min: 7.2%2026 · 1–4 hr: 9.6%2026 · 4–8 hr: 2.2%2026 · Over 8 hr: 0.2%2009n=3332011n=4932013n=5062015n=6332017n=6402019n=5902021n=5952023n=6952025n=6112026n=417
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
20093331.8%60.7%30.3%3.3%3.6%0.3%—
20104741.9%62.2%31.6%3.2%1.1%——
20114932.8%62.5%28.0%3.5%2.4%0.6%0.2%
20124812.1%59.5%30.4%4.2%3.8%0.2%—
20135062.6%58.7%33.4%2.2%3.0%0.2%—
20145163.3%53.7%35.3%3.5%4.1%0.2%—
20156332.8%54.3%36.0%3.2%3.0%0.6%—
20166153.1%50.1%40.2%3.6%3.1%——
20176403.4%45.6%45.2%2.2%3.3%0.3%—
20186584.1%42.7%42.4%5.0%5.2%0.6%—
20195904.6%43.9%42.9%2.9%5.1%0.7%—
20205326.0%39.7%44.9%3.8%5.1%0.6%—
20215954.7%37.1%47.2%4.5%5.0%1.3%—
20226904.1%30.6%53.8%4.3%6.2%1.0%—
20236954.8%32.8%49.6%4.2%6.5%1.6%0.6%
20246406.4%28.9%47.3%6.1%9.4%0.9%0.9%
20256114.9%26.2%44.8%7.7%12.4%3.1%0.8%
20264173.8%26.9%50.1%7.2%9.6%2.2%0.2%
The Average Call Waits 27 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 27 minutes in 2026, more than double what it was in 2016. 12% of calls took more than an hour to get a response in 2026, compared with 3% 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.