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

Suspicious Circumstances

Suspicious Circumstances calls over time: volume, outcomes, and response speed

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

Swipe sideways to see the full chart →
040,00080,0002009: 29,898 suspicious circumstances calls logged in CAD2010: 55,911 suspicious circumstances calls logged in CAD2011: 47,935 suspicious circumstances calls logged in CAD2012: 47,461 suspicious circumstances calls logged in CAD2013: 45,734 suspicious circumstances calls logged in CAD2014: 41,453 suspicious circumstances calls logged in CAD2015: 42,114 suspicious circumstances calls logged in CAD2016: 43,907 suspicious circumstances calls logged in CAD2017: 42,483 suspicious circumstances calls logged in CAD2018: 42,738 suspicious circumstances calls logged in CAD2019: 41,389 suspicious circumstances calls logged in CAD2020: 32,314 suspicious circumstances calls logged in CAD2021: 34,277 suspicious circumstances calls logged in CAD2022: 40,416 suspicious circumstances calls logged in CAD2023: 40,157 suspicious circumstances calls logged in CAD2024: 40,104 suspicious circumstances calls logged in CAD2025: 42,017 suspicious circumstances calls logged in CAD2026: 29,826 suspicious circumstances calls logged in CAD2009n=29,8982011n=47,9352013n=45,7342015n=42,1142017n=42,4832019n=41,3892021n=34,2772023n=40,1572025n=42,0172026n=29,826
suspicious circumstances calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodSuspicious circumstances calls logged in CAD
200929,898
201055,911
201147,935
201247,461
201345,734
201441,453
201542,114
201643,907
201742,483
201842,738
201941,389
202032,314
202134,277
202240,416
202340,157
202440,104
202542,017
202629,826
Calls for Suspicious Circumstances Are Down 25% From Their 2010 PeakSeattle Police logged 55,911 suspicious circumstances calls in 2010 and 42,017 in 2025, the most recent full year.

Suspicious Circumstances: 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.8%2009 · Report taken, no arrest: 6.4%2009 · Resolved on scene: 81.8%2009 · Unable to locate: 9.0%2009 · Other (unfounded / cancelled): 2.1%2010 · Arrest / citation: 0.5%2010 · Report taken, no arrest: 7.7%2010 · Resolved on scene: 81.1%2010 · Unable to locate: 8.9%2010 · Other (unfounded / cancelled): 1.8%2011 · Arrest / citation: 0.3%2011 · Report taken, no arrest: 10.1%2011 · Resolved on scene: 77.0%2011 · Unable to locate: 10.9%2011 · Other (unfounded / cancelled): 1.7%2012 · Arrest / citation: 0.2%2012 · Report taken, no arrest: 8.9%2012 · Resolved on scene: 77.0%2012 · Unable to locate: 12.3%2012 · Other (unfounded / cancelled): 1.6%2013 · Arrest / citation: 0.2%2013 · Report taken, no arrest: 9.1%2013 · Resolved on scene: 74.6%2013 · Unable to locate: 14.4%2013 · Other (unfounded / cancelled): 1.7%2014 · Arrest / citation: 0.2%2014 · Report taken, no arrest: 10.9%2014 · Resolved on scene: 68.4%2014 · Unable to locate: 19.0%2014 · Other (unfounded / cancelled): 1.6%2015 · Arrest / citation: 0.2%2015 · Report taken, no arrest: 12.8%2015 · Resolved on scene: 63.2%2015 · Unable to locate: 22.2%2015 · Other (unfounded / cancelled): 1.6%2016 · Arrest / citation: 0.2%2016 · Report taken, no arrest: 12.8%2016 · Resolved on scene: 62.4%2016 · Unable to locate: 22.6%2016 · Other (unfounded / cancelled): 2.1%2017 · Arrest / citation: 0.2%2017 · Report taken, no arrest: 12.7%2017 · Resolved on scene: 62.3%2017 · Unable to locate: 22.8%2017 · Other (unfounded / cancelled): 2.0%2018 · Arrest / citation: 0.2%2018 · Report taken, no arrest: 14.1%2018 · Resolved on scene: 59.3%2018 · Unable to locate: 24.4%2018 · Other (unfounded / cancelled): 1.9%2019 · Arrest / citation: 0.3%2019 · Report taken, no arrest: 13.7%2019 · Resolved on scene: 56.9%2019 · Unable to locate: 27.3%2019 · Other (unfounded / cancelled): 1.9%2020 · Arrest / citation: 0.3%2020 · Report taken, no arrest: 14.3%2020 · Resolved on scene: 55.8%2020 · Unable to locate: 27.7%2020 · Other (unfounded / cancelled): 1.9%2021 · Arrest / citation: 0.2%2021 · Report taken, no arrest: 13.4%2021 · Resolved on scene: 54.9%2021 · Unable to locate: 29.8%2021 · Other (unfounded / cancelled): 1.7%2022 · Arrest / citation: 0.2%2022 · Report taken, no arrest: 12.2%2022 · Resolved on scene: 50.5%2022 · Unable to locate: 35.8%2022 · Other (unfounded / cancelled): 1.3%2023 · Arrest / citation: 0.1%2023 · Report taken, no arrest: 12.5%2023 · Resolved on scene: 45.2%2023 · Unable to locate: 40.8%2023 · Other (unfounded / cancelled): 1.4%2024 · Arrest / citation: 0.2%2024 · Report taken, no arrest: 12.1%2024 · Resolved on scene: 42.5%2024 · Unable to locate: 43.9%2024 · Other (unfounded / cancelled): 1.3%2025 · Arrest / citation: 0.3%2025 · Report taken, no arrest: 12.4%2025 · Resolved on scene: 43.3%2025 · Unable to locate: 42.6%2025 · Other (unfounded / cancelled): 1.4%2026 · Arrest / citation: 0.4%2026 · Report taken, no arrest: 14.2%2026 · Resolved on scene: 41.1%2026 · Unable to locate: 42.9%2026 · Other (unfounded / cancelled): 1.4%2009n=29,8982011n=47,9352013n=45,7342015n=42,1142017n=42,4832019n=41,3892021n=34,2772023n=40,1572025n=42,0172026n=29,826
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)
200929,8980.8%6.4%81.8%9.0%2.1%
201055,9110.5%7.7%81.1%8.9%1.8%
201147,9350.3%10.1%77.0%10.9%1.7%
201247,4610.2%8.9%77.0%12.3%1.6%
201345,7340.2%9.1%74.6%14.4%1.7%
201441,4530.2%10.9%68.4%19.0%1.6%
201542,1140.2%12.8%63.2%22.2%1.6%
201643,9070.2%12.8%62.4%22.6%2.1%
201742,4830.2%12.7%62.3%22.8%2.0%
201842,7380.2%14.1%59.3%24.4%1.9%
201941,3890.3%13.7%56.9%27.3%1.9%
202032,3140.3%14.3%55.8%27.7%1.9%
202134,2770.2%13.4%54.9%29.8%1.7%
202240,4160.2%12.2%50.5%35.8%1.3%
202340,1570.1%12.5%45.2%40.8%1.4%
202440,1040.2%12.1%42.5%43.9%1.3%
202542,0170.3%12.4%43.3%42.6%1.4%
202629,8260.4%14.2%41.1%42.9%1.4%
43% of Calls for Suspicious Circumstances End “Unable to Locate,” Up From 23%Report-taken outcomes moved from 13% of calls in 2016 to 14% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Suspicious Circumstances: 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 25% of suspicious circumstances 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.1 min2010: 19.8 min2011: 20.0 min2012: 26.4 min2013: 27.8 min2014: 32.9 min2015: 45.3 min2016: 39.1 min2017: 38.6 min2018: 51.1 min2019: 44.6 min2020: 38.5 min2021: 52.0 min2022: 60.5 min2023: 79.1 min2024: 110.1 min2025: 100.3 min2026: 92.8 min2009: 30.8 min2010: 26.1 min2011: 26.8 min2012: 33.1 min2013: 34.6 min2014: 40.4 min2015: 52.6 min2016: 46.8 min2017: 46.5 min2018: 59.5 min2019: 53.0 min2020: 47.2 min2021: 61.4 min2022: 68.2 min2023: 89.1 min2024: 118.9 min2025: 108.7 min2026: 101.1 min2009n=15,2762011n=28,0072013n=34,2202015n=35,1002017n=32,7432019n=33,1202021n=28,5242023n=34,1552025n=35,6502026n=25,165
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
200915,27625.1 min30.8 min
201025,86819.8 min26.1 min
201128,00720.0 min26.8 min
201231,27726.4 min33.1 min
201334,22027.8 min34.6 min
201434,31632.9 min40.4 min
201535,10045.3 min52.6 min
201635,19539.1 min46.8 min
201732,74338.6 min46.5 min
201834,09051.1 min59.5 min
201933,12044.6 min53.0 min
202025,79238.5 min47.2 min
202128,52452.0 min61.4 min
202233,20160.5 min68.2 min
202334,15579.1 min89.1 min
202434,015110.1 min118.9 min
202535,650100.3 min108.7 min
202625,16592.8 min101.1 min
The Average Call Waits 101 Minutes for an Officer to ArriveAverage response time has more than doubled in the past 10 years, from 47 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.

Suspicious Circumstances: 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 25% of suspicious circumstances 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: 6.6%2009 · 0–5 min: 17.5%2009 · 5–30 min: 49.0%2009 · 30–60 min: 13.0%2009 · 1–4 hr: 13.0%2009 · 4–8 hr: 0.8%2009 · Over 8 hr: 0.0%2010 · No recorded response: 6.4%2010 · 0–5 min: 20.1%2010 · 5–30 min: 51.1%2010 · 30–60 min: 11.9%2010 · 1–4 hr: 10.0%2010 · 4–8 hr: 0.4%2010 · Over 8 hr: 0.0%2011 · No recorded response: 6.4%2011 · 0–5 min: 19.8%2011 · 5–30 min: 50.8%2011 · 30–60 min: 12.0%2011 · 1–4 hr: 10.5%2011 · 4–8 hr: 0.5%2011 · Over 8 hr: 0.0%2012 · No recorded response: 6.4%2012 · 0–5 min: 17.5%2012 · 5–30 min: 48.2%2012 · 30–60 min: 13.0%2012 · 1–4 hr: 13.8%2012 · 4–8 hr: 0.9%2012 · Over 8 hr: 0.1%2013 · No recorded response: 6.2%2013 · 0–5 min: 17.0%2013 · 5–30 min: 47.5%2013 · 30–60 min: 13.4%2013 · 1–4 hr: 14.7%2013 · 4–8 hr: 1.1%2013 · Over 8 hr: 0.1%2014 · No recorded response: 6.3%2014 · 0–5 min: 15.0%2014 · 5–30 min: 46.9%2014 · 30–60 min: 13.2%2014 · 1–4 hr: 16.9%2014 · 4–8 hr: 1.7%2014 · Over 8 hr: 0.1%2015 · No recorded response: 6.7%2015 · 0–5 min: 12.7%2015 · 5–30 min: 42.8%2015 · 30–60 min: 13.9%2015 · 1–4 hr: 20.5%2015 · 4–8 hr: 3.0%2015 · Over 8 hr: 0.5%2016 · No recorded response: 6.0%2016 · 0–5 min: 13.0%2016 · 5–30 min: 45.0%2016 · 30–60 min: 14.2%2016 · 1–4 hr: 19.1%2016 · 4–8 hr: 2.4%2016 · Over 8 hr: 0.3%2017 · No recorded response: 6.0%2017 · 0–5 min: 12.4%2017 · 5–30 min: 45.2%2017 · 30–60 min: 14.1%2017 · 1–4 hr: 19.8%2017 · 4–8 hr: 2.3%2017 · Over 8 hr: 0.2%2018 · No recorded response: 7.0%2018 · 0–5 min: 11.0%2018 · 5–30 min: 40.6%2018 · 30–60 min: 14.0%2018 · 1–4 hr: 22.9%2018 · 4–8 hr: 3.8%2018 · Over 8 hr: 0.6%2019 · No recorded response: 7.0%2019 · 0–5 min: 11.3%2019 · 5–30 min: 42.2%2019 · 30–60 min: 14.8%2019 · 1–4 hr: 21.5%2019 · 4–8 hr: 2.8%2019 · Over 8 hr: 0.4%2020 · No recorded response: 7.2%2020 · 0–5 min: 12.6%2020 · 5–30 min: 45.0%2020 · 30–60 min: 13.5%2020 · 1–4 hr: 18.9%2020 · 4–8 hr: 2.5%2020 · Over 8 hr: 0.3%2021 · No recorded response: 8.4%2021 · 0–5 min: 9.5%2021 · 5–30 min: 41.4%2021 · 30–60 min: 13.9%2021 · 1–4 hr: 22.1%2021 · 4–8 hr: 3.8%2021 · Over 8 hr: 0.8%2022 · No recorded response: 11.1%2022 · 0–5 min: 9.1%2022 · 5–30 min: 37.2%2022 · 30–60 min: 13.8%2022 · 1–4 hr: 23.4%2022 · 4–8 hr: 4.4%2022 · Over 8 hr: 1.0%2023 · No recorded response: 11.4%2023 · 0–5 min: 7.8%2023 · 5–30 min: 35.4%2023 · 30–60 min: 12.4%2023 · 1–4 hr: 24.0%2023 · 4–8 hr: 6.7%2023 · Over 8 hr: 2.3%2024 · No recorded response: 10.8%2024 · 0–5 min: 5.6%2024 · 5–30 min: 28.3%2024 · 30–60 min: 13.3%2024 · 1–4 hr: 29.1%2024 · 4–8 hr: 9.2%2024 · Over 8 hr: 3.9%2025 · No recorded response: 8.7%2025 · 0–5 min: 6.6%2025 · 5–30 min: 30.1%2025 · 30–60 min: 14.1%2025 · 1–4 hr: 28.8%2025 · 4–8 hr: 8.2%2025 · Over 8 hr: 3.5%2026 · No recorded response: 7.1%2026 · 0–5 min: 7.2%2026 · 5–30 min: 33.0%2026 · 30–60 min: 14.3%2026 · 1–4 hr: 27.4%2026 · 4–8 hr: 7.8%2026 · Over 8 hr: 3.2%2009n=15,2762011n=28,0072013n=34,2202015n=35,1002017n=32,7432019n=33,1202021n=28,5242023n=34,1552025n=35,6502026n=25,165
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
200915,2766.6%17.5%49.0%13.0%13.0%0.8%0.0%
201025,8686.4%20.1%51.1%11.9%10.0%0.4%0.0%
201128,0076.4%19.8%50.8%12.0%10.5%0.5%0.0%
201231,2776.4%17.5%48.2%13.0%13.8%0.9%0.1%
201334,2206.2%17.0%47.5%13.4%14.7%1.1%0.1%
201434,3166.3%15.0%46.9%13.2%16.9%1.7%0.1%
201535,1006.7%12.7%42.8%13.9%20.5%3.0%0.5%
201635,1956.0%13.0%45.0%14.2%19.1%2.4%0.3%
201732,7436.0%12.4%45.2%14.1%19.8%2.3%0.2%
201834,0907.0%11.0%40.6%14.0%22.9%3.8%0.6%
201933,1207.0%11.3%42.2%14.8%21.5%2.8%0.4%
202025,7927.2%12.6%45.0%13.5%18.9%2.5%0.3%
202128,5248.4%9.5%41.4%13.9%22.1%3.8%0.8%
202233,20111.1%9.1%37.2%13.8%23.4%4.4%1.0%
202334,15511.4%7.8%35.4%12.4%24.0%6.7%2.3%
202434,01510.8%5.6%28.3%13.3%29.1%9.2%3.9%
202535,6508.7%6.6%30.1%14.1%28.8%8.2%3.5%
202625,1657.1%7.2%33.0%14.3%27.4%7.8%3.2%
The Average Call Waits 93 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 93 minutes in 2026, more than double what it was in 2016. 38% of calls took more than an hour to get a response in 2026, compared with 22% 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.