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

All Police Calls

All police calls over time: volume, outcomes, and response speed

All Police Calls: 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 (36% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
0250,000500,0002009: 229,435 calls logged in CAD (all categories)2010: 408,921 calls logged in CAD (all categories)2011: 379,906 calls logged in CAD (all categories)2012: 404,441 calls logged in CAD (all categories)2013: 424,407 calls logged in CAD (all categories)2014: 384,374 calls logged in CAD (all categories)2015: 400,929 calls logged in CAD (all categories)2016: 420,171 calls logged in CAD (all categories)2017: 432,487 calls logged in CAD (all categories)2018: 434,672 calls logged in CAD (all categories)2019: 432,392 calls logged in CAD (all categories)2020: 317,826 calls logged in CAD (all categories)2021: 304,674 calls logged in CAD (all categories)2022: 318,075 calls logged in CAD (all categories)2023: 339,690 calls logged in CAD (all categories)2024: 325,828 calls logged in CAD (all categories)2025: 339,080 calls logged in CAD (all categories)2026: 243,964 calls logged in CAD (all categories)2009n=229,4352011n=379,9062013n=424,4072015n=400,9292017n=432,4872019n=432,3922021n=304,6742023n=339,6902025n=339,0802026n=243,964
calls logged in CAD (all categories)
View as table
Call volume — same numbers as the chart above
PeriodCalls logged in CAD
2009229,435
2010408,921
2011379,906
2012404,441
2013424,407
2014384,374
2015400,929
2016420,171
2017432,487
2018434,672
2019432,392
2020317,826
2021304,674
2022318,075
2023339,690
2024325,828
2025339,080
2026243,964
All Calls Are Down 22% From Their 2018 PeakSeattle Police logged 434,672 calls in 2018 and 339,080 in 2025, the most recent full year.

All Police Calls: 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: 11.1%2009 · Report taken, no arrest: 25.6%2009 · Resolved on scene: 51.0%2009 · Unable to locate: 6.9%2009 · Other (unfounded / cancelled): 5.4%2010 · Arrest / citation: 10.8%2010 · Report taken, no arrest: 24.6%2010 · Resolved on scene: 53.7%2010 · Unable to locate: 6.3%2010 · Other (unfounded / cancelled): 4.5%2011 · Arrest / citation: 8.9%2011 · Report taken, no arrest: 24.0%2011 · Resolved on scene: 55.6%2011 · Unable to locate: 6.8%2011 · Other (unfounded / cancelled): 4.8%2012 · Arrest / citation: 7.1%2012 · Report taken, no arrest: 22.4%2012 · Resolved on scene: 59.2%2012 · Unable to locate: 7.0%2012 · Other (unfounded / cancelled): 4.3%2013 · Arrest / citation: 6.7%2013 · Report taken, no arrest: 22.2%2013 · Resolved on scene: 59.4%2013 · Unable to locate: 7.4%2013 · Other (unfounded / cancelled): 4.2%2014 · Arrest / citation: 6.9%2014 · Report taken, no arrest: 27.1%2014 · Resolved on scene: 51.7%2014 · Unable to locate: 9.5%2014 · Other (unfounded / cancelled): 4.8%2015 · Arrest / citation: 7.8%2015 · Report taken, no arrest: 27.2%2015 · Resolved on scene: 49.8%2015 · Unable to locate: 10.5%2015 · Other (unfounded / cancelled): 4.7%2016 · Arrest / citation: 7.9%2016 · Report taken, no arrest: 26.0%2016 · Resolved on scene: 51.2%2016 · Unable to locate: 10.2%2016 · Other (unfounded / cancelled): 4.7%2017 · Arrest / citation: 8.0%2017 · Report taken, no arrest: 25.4%2017 · Resolved on scene: 52.0%2017 · Unable to locate: 9.8%2017 · Other (unfounded / cancelled): 4.7%2018 · Arrest / citation: 8.9%2018 · Report taken, no arrest: 25.5%2018 · Resolved on scene: 50.1%2018 · Unable to locate: 10.8%2018 · Other (unfounded / cancelled): 4.7%2019 · Arrest / citation: 10.3%2019 · Report taken, no arrest: 24.2%2019 · Resolved on scene: 49.1%2019 · Unable to locate: 11.7%2019 · Other (unfounded / cancelled): 4.7%2020 · Arrest / citation: 7.7%2020 · Report taken, no arrest: 27.7%2020 · Resolved on scene: 48.2%2020 · Unable to locate: 11.7%2020 · Other (unfounded / cancelled): 4.7%2021 · Arrest / citation: 6.9%2021 · Report taken, no arrest: 27.9%2021 · Resolved on scene: 45.5%2021 · Unable to locate: 14.6%2021 · Other (unfounded / cancelled): 5.1%2022 · Arrest / citation: 5.2%2022 · Report taken, no arrest: 27.3%2022 · Resolved on scene: 44.3%2022 · Unable to locate: 18.1%2022 · Other (unfounded / cancelled): 5.0%2023 · Arrest / citation: 5.1%2023 · Report taken, no arrest: 26.3%2023 · Resolved on scene: 43.1%2023 · Unable to locate: 20.0%2023 · Other (unfounded / cancelled): 5.5%2024 · Arrest / citation: 6.0%2024 · Report taken, no arrest: 25.2%2024 · Resolved on scene: 41.3%2024 · Unable to locate: 23.0%2024 · Other (unfounded / cancelled): 4.6%2025 · Arrest / citation: 8.2%2025 · Report taken, no arrest: 22.5%2025 · Resolved on scene: 43.5%2025 · Unable to locate: 22.9%2025 · Other (unfounded / cancelled): 2.8%2026 · Arrest / citation: 9.6%2026 · Report taken, no arrest: 21.7%2026 · Resolved on scene: 42.3%2026 · Unable to locate: 23.5%2026 · Other (unfounded / cancelled): 2.8%2009n=229,4352011n=379,9062013n=424,4072015n=400,9292017n=432,4872019n=432,3922021n=304,6742023n=339,6902025n=339,0802026n=243,964
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)
2009229,43511.1%25.6%51.0%6.9%5.4%
2010408,92110.8%24.6%53.7%6.3%4.5%
2011379,9068.9%24.0%55.6%6.8%4.8%
2012404,4417.1%22.4%59.2%7.0%4.3%
2013424,4076.7%22.2%59.4%7.4%4.2%
2014384,3746.9%27.1%51.7%9.5%4.8%
2015400,9297.8%27.2%49.8%10.5%4.7%
2016420,1717.9%26.0%51.2%10.2%4.7%
2017432,4878.0%25.4%52.0%9.8%4.7%
2018434,6728.9%25.5%50.1%10.8%4.7%
2019432,39210.3%24.2%49.1%11.7%4.7%
2020317,8267.7%27.7%48.2%11.7%4.7%
2021304,6746.9%27.9%45.5%14.6%5.1%
2022318,0755.2%27.3%44.3%18.1%5.0%
2023339,6905.1%26.3%43.1%20.0%5.5%
2024325,8286.0%25.2%41.3%23.0%4.6%
2025339,0808.2%22.5%43.5%22.9%2.8%
2026243,9649.6%21.7%42.3%23.5%2.8%
24% of All Calls End “Unable to Locate,” Up From 10%Report-taken outcomes moved from 26% of calls in 2016 to 22% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

All Police Calls: 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 36% of all 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: 26.5 min2010: 20.0 min2011: 20.1 min2012: 25.2 min2013: 27.7 min2014: 34.1 min2015: 39.9 min2016: 35.7 min2017: 36.6 min2018: 45.2 min2019: 42.0 min2020: 35.9 min2021: 49.7 min2022: 56.3 min2023: 72.1 min2024: 97.0 min2025: 92.1 min2026: 89.6 min2009: 34.5 min2010: 28.0 min2011: 29.4 min2012: 34.9 min2013: 37.8 min2014: 45.3 min2015: 50.6 min2016: 46.4 min2017: 47.5 min2018: 57.0 min2019: 53.5 min2020: 46.6 min2021: 61.8 min2022: 66.6 min2023: 83.4 min2024: 108.0 min2025: 103.7 min2026: 101.3 min2009n=134,3442011n=220,2862013n=247,5572015n=261,2462017n=262,0182019n=257,9572021n=224,3162023n=251,4732025n=241,2362026n=174,910
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
2009134,34426.5 min34.5 min
2010220,19820.0 min28.0 min
2011220,28620.1 min29.4 min
2012233,85225.2 min34.9 min
2013247,55727.7 min37.8 min
2014255,50434.1 min45.3 min
2015261,24639.9 min50.6 min
2016264,96735.7 min46.4 min
2017262,01836.6 min47.5 min
2018267,20545.2 min57.0 min
2019257,95742.0 min53.5 min
2020207,48935.9 min46.6 min
2021224,31649.7 min61.8 min
2022232,33456.3 min66.6 min
2023251,47372.1 min83.4 min
2024241,20097.0 min108.0 min
2025241,23692.1 min103.7 min
2026174,91089.6 min101.3 min
The Average Call Waits 101 Minutes for an Officer to ArriveDespite a 19% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 46 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.

All Police Calls: 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 36% of all 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: 13.6%2009 · 0–5 min: 16.2%2009 · 5–30 min: 42.5%2009 · 30–60 min: 13.2%2009 · 1–4 hr: 13.5%2009 · 4–8 hr: 0.9%2009 · Over 8 hr: 0.1%2010 · No recorded response: 14.2%2010 · 0–5 min: 19.6%2010 · 5–30 min: 44.1%2010 · 30–60 min: 11.4%2010 · 1–4 hr: 10.1%2010 · 4–8 hr: 0.5%2010 · Over 8 hr: 0.0%2011 · No recorded response: 14.9%2011 · 0–5 min: 19.0%2011 · 5–30 min: 43.5%2011 · 30–60 min: 11.2%2011 · 1–4 hr: 10.8%2011 · 4–8 hr: 0.6%2011 · Over 8 hr: 0.0%2012 · No recorded response: 14.5%2012 · 0–5 min: 17.2%2012 · 5–30 min: 41.9%2012 · 30–60 min: 12.0%2012 · 1–4 hr: 13.3%2012 · 4–8 hr: 1.1%2012 · Over 8 hr: 0.1%2013 · No recorded response: 14.0%2013 · 0–5 min: 16.9%2013 · 5–30 min: 41.4%2013 · 30–60 min: 12.1%2013 · 1–4 hr: 14.2%2013 · 4–8 hr: 1.3%2013 · Over 8 hr: 0.2%2014 · No recorded response: 14.0%2014 · 0–5 min: 14.7%2014 · 5–30 min: 40.5%2014 · 30–60 min: 12.0%2014 · 1–4 hr: 16.3%2014 · 4–8 hr: 2.3%2014 · Over 8 hr: 0.2%2015 · No recorded response: 13.1%2015 · 0–5 min: 15.3%2015 · 5–30 min: 39.0%2015 · 30–60 min: 11.8%2015 · 1–4 hr: 17.5%2015 · 4–8 hr: 2.9%2015 · Over 8 hr: 0.5%2016 · No recorded response: 12.9%2016 · 0–5 min: 15.8%2016 · 5–30 min: 40.3%2016 · 30–60 min: 11.7%2016 · 1–4 hr: 16.4%2016 · 4–8 hr: 2.5%2016 · Over 8 hr: 0.3%2017 · No recorded response: 12.5%2017 · 0–5 min: 15.3%2017 · 5–30 min: 40.8%2017 · 30–60 min: 11.8%2017 · 1–4 hr: 16.9%2017 · 4–8 hr: 2.4%2017 · Over 8 hr: 0.3%2018 · No recorded response: 13.2%2018 · 0–5 min: 13.7%2018 · 5–30 min: 37.5%2018 · 30–60 min: 11.9%2018 · 1–4 hr: 19.4%2018 · 4–8 hr: 3.8%2018 · Over 8 hr: 0.5%2019 · No recorded response: 13.4%2019 · 0–5 min: 14.1%2019 · 5–30 min: 38.5%2019 · 30–60 min: 11.9%2019 · 1–4 hr: 18.7%2019 · 4–8 hr: 3.0%2019 · Over 8 hr: 0.5%2020 · No recorded response: 12.5%2020 · 0–5 min: 15.2%2020 · 5–30 min: 41.4%2020 · 30–60 min: 11.3%2020 · 1–4 hr: 16.7%2020 · 4–8 hr: 2.5%2020 · Over 8 hr: 0.4%2021 · No recorded response: 14.3%2021 · 0–5 min: 11.9%2021 · 5–30 min: 38.7%2021 · 30–60 min: 11.4%2021 · 1–4 hr: 18.8%2021 · 4–8 hr: 3.9%2021 · Over 8 hr: 1.0%2022 · No recorded response: 13.2%2022 · 0–5 min: 12.1%2022 · 5–30 min: 37.3%2022 · 30–60 min: 11.7%2022 · 1–4 hr: 20.2%2022 · 4–8 hr: 4.3%2022 · Over 8 hr: 1.2%2023 · No recorded response: 14.7%2023 · 0–5 min: 11.4%2023 · 5–30 min: 35.5%2023 · 30–60 min: 10.8%2023 · 1–4 hr: 19.5%2023 · 4–8 hr: 5.6%2023 · Over 8 hr: 2.5%2024 · No recorded response: 14.3%2024 · 0–5 min: 9.3%2024 · 5–30 min: 30.5%2024 · 30–60 min: 11.1%2024 · 1–4 hr: 23.2%2024 · 4–8 hr: 7.8%2024 · Over 8 hr: 3.6%2025 · No recorded response: 14.0%2025 · 0–5 min: 10.8%2025 · 5–30 min: 30.8%2025 · 30–60 min: 11.3%2025 · 1–4 hr: 22.4%2025 · 4–8 hr: 7.2%2025 · Over 8 hr: 3.5%2026 · No recorded response: 15.1%2026 · 0–5 min: 9.9%2026 · 5–30 min: 32.4%2026 · 30–60 min: 11.5%2026 · 1–4 hr: 20.8%2026 · 4–8 hr: 6.9%2026 · Over 8 hr: 3.4%2009n=134,3442011n=220,2862013n=247,5572015n=261,2462017n=262,0182019n=257,9572021n=224,3162023n=251,4732025n=241,2362026n=174,910
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
2009134,34413.6%16.2%42.5%13.2%13.5%0.9%0.1%
2010220,19814.2%19.6%44.1%11.4%10.1%0.5%0.0%
2011220,28614.9%19.0%43.5%11.2%10.8%0.6%0.0%
2012233,85214.5%17.2%41.9%12.0%13.3%1.1%0.1%
2013247,55714.0%16.9%41.4%12.1%14.2%1.3%0.2%
2014255,50414.0%14.7%40.5%12.0%16.3%2.3%0.2%
2015261,24613.1%15.3%39.0%11.8%17.5%2.9%0.5%
2016264,96712.9%15.8%40.3%11.7%16.4%2.5%0.3%
2017262,01812.5%15.3%40.8%11.8%16.9%2.4%0.3%
2018267,20513.2%13.7%37.5%11.9%19.4%3.8%0.5%
2019257,95713.4%14.1%38.5%11.9%18.7%3.0%0.5%
2020207,48912.5%15.2%41.4%11.3%16.7%2.5%0.4%
2021224,31614.3%11.9%38.7%11.4%18.8%3.9%1.0%
2022232,33413.2%12.1%37.3%11.7%20.2%4.3%1.2%
2023251,47314.7%11.4%35.5%10.8%19.5%5.6%2.5%
2024241,20014.3%9.3%30.5%11.1%23.2%7.8%3.6%
2025241,23614.0%10.8%30.8%11.3%22.4%7.2%3.5%
2026174,91015.1%9.9%32.4%11.5%20.8%6.9%3.4%
The Average Call Waits 90 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 90 minutes in 2026, more than double what it was in 2016. 31% of calls took more than an hour to get a response in 2026, compared with 19% 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 calls logged in CAD (all categories) that year. 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.