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

Theft

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

Theft: 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 →
015,00030,0002009: 17,625 theft calls logged in CAD2010: 25,111 theft calls logged in CAD2011: 21,529 theft calls logged in CAD2012: 21,959 theft calls logged in CAD2013: 23,836 theft calls logged in CAD2014: 26,138 theft calls logged in CAD2015: 24,778 theft calls logged in CAD2016: 24,167 theft calls logged in CAD2017: 23,399 theft calls logged in CAD2018: 22,454 theft calls logged in CAD2019: 18,139 theft calls logged in CAD2020: 13,351 theft calls logged in CAD2021: 14,675 theft calls logged in CAD2022: 13,909 theft calls logged in CAD2023: 14,028 theft calls logged in CAD2024: 14,378 theft calls logged in CAD2025: 14,355 theft calls logged in CAD2026: 10,047 theft calls logged in CAD2009n=17,6252011n=21,5292013n=23,8362015n=24,7782017n=23,3992019n=18,1392021n=14,6752023n=14,0282025n=14,3552026n=10,047
theft calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodTheft calls logged in CAD
200917,625
201025,111
201121,529
201221,959
201323,836
201426,138
201524,778
201624,167
201723,399
201822,454
201918,139
202013,351
202114,675
202213,909
202314,028
202414,378
202514,355
202610,047
Theft Calls Are Down 45% From Their 2014 PeakSeattle Police logged 26,138 theft calls in 2014 and 14,355 in 2025, the most recent full year.

Theft: 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: 2.9%2009 · Report taken, no arrest: 75.9%2009 · Resolved on scene: 12.1%2009 · Unable to locate: 2.7%2009 · Other (unfounded / cancelled): 6.4%2010 · Arrest / citation: 3.6%2010 · Report taken, no arrest: 75.5%2010 · Resolved on scene: 13.0%2010 · Unable to locate: 2.8%2010 · Other (unfounded / cancelled): 5.1%2011 · Arrest / citation: 4.4%2011 · Report taken, no arrest: 71.3%2011 · Resolved on scene: 16.8%2011 · Unable to locate: 3.0%2011 · Other (unfounded / cancelled): 4.6%2012 · Arrest / citation: 4.0%2012 · Report taken, no arrest: 70.1%2012 · Resolved on scene: 17.6%2012 · Unable to locate: 3.6%2012 · Other (unfounded / cancelled): 4.6%2013 · Arrest / citation: 3.6%2013 · Report taken, no arrest: 69.1%2013 · Resolved on scene: 18.5%2013 · Unable to locate: 6.1%2013 · Other (unfounded / cancelled): 2.7%2014 · Arrest / citation: 2.6%2014 · Report taken, no arrest: 70.4%2014 · Resolved on scene: 17.0%2014 · Unable to locate: 7.9%2014 · Other (unfounded / cancelled): 2.2%2015 · Arrest / citation: 2.9%2015 · Report taken, no arrest: 71.2%2015 · Resolved on scene: 15.9%2015 · Unable to locate: 7.8%2015 · Other (unfounded / cancelled): 2.2%2016 · Arrest / citation: 3.7%2016 · Report taken, no arrest: 69.9%2016 · Resolved on scene: 17.0%2016 · Unable to locate: 7.2%2016 · Other (unfounded / cancelled): 2.2%2017 · Arrest / citation: 3.9%2017 · Report taken, no arrest: 68.6%2017 · Resolved on scene: 17.7%2017 · Unable to locate: 7.3%2017 · Other (unfounded / cancelled): 2.5%2018 · Arrest / citation: 4.0%2018 · Report taken, no arrest: 67.6%2018 · Resolved on scene: 18.0%2018 · Unable to locate: 8.2%2018 · Other (unfounded / cancelled): 2.2%2019 · Arrest / citation: 5.7%2019 · Report taken, no arrest: 63.5%2019 · Resolved on scene: 19.5%2019 · Unable to locate: 9.4%2019 · Other (unfounded / cancelled): 1.9%2020 · Arrest / citation: 3.9%2020 · Report taken, no arrest: 63.2%2020 · Resolved on scene: 20.5%2020 · Unable to locate: 10.7%2020 · Other (unfounded / cancelled): 1.8%2021 · Arrest / citation: 3.7%2021 · Report taken, no arrest: 59.7%2021 · Resolved on scene: 23.0%2021 · Unable to locate: 12.1%2021 · Other (unfounded / cancelled): 1.5%2022 · Arrest / citation: 5.3%2022 · Report taken, no arrest: 57.5%2022 · Resolved on scene: 21.5%2022 · Unable to locate: 14.5%2022 · Other (unfounded / cancelled): 1.2%2023 · Arrest / citation: 3.5%2023 · Report taken, no arrest: 56.7%2023 · Resolved on scene: 19.5%2023 · Unable to locate: 19.2%2023 · Other (unfounded / cancelled): 1.2%2024 · Arrest / citation: 3.6%2024 · Report taken, no arrest: 51.4%2024 · Resolved on scene: 20.9%2024 · Unable to locate: 23.0%2024 · Other (unfounded / cancelled): 1.0%2025 · Arrest / citation: 4.6%2025 · Report taken, no arrest: 49.8%2025 · Resolved on scene: 21.1%2025 · Unable to locate: 23.0%2025 · Other (unfounded / cancelled): 1.4%2026 · Arrest / citation: 6.0%2026 · Report taken, no arrest: 51.4%2026 · Resolved on scene: 19.0%2026 · Unable to locate: 22.3%2026 · Other (unfounded / cancelled): 1.4%2009n=17,6252011n=21,5292013n=23,8362015n=24,7782017n=23,3992019n=18,1392021n=14,6752023n=14,0282025n=14,3552026n=10,047
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)
200917,6252.9%75.9%12.1%2.7%6.4%
201025,1113.6%75.5%13.0%2.8%5.1%
201121,5294.4%71.3%16.8%3.0%4.6%
201221,9594.0%70.1%17.6%3.6%4.6%
201323,8363.6%69.1%18.5%6.1%2.7%
201426,1382.6%70.4%17.0%7.9%2.2%
201524,7782.9%71.2%15.9%7.8%2.2%
201624,1673.7%69.9%17.0%7.2%2.2%
201723,3993.9%68.6%17.7%7.3%2.5%
201822,4544.0%67.6%18.0%8.2%2.2%
201918,1395.7%63.5%19.5%9.4%1.9%
202013,3513.9%63.2%20.5%10.7%1.8%
202114,6753.7%59.7%23.0%12.1%1.5%
202213,9095.3%57.5%21.5%14.5%1.2%
202314,0283.5%56.7%19.5%19.2%1.2%
202414,3783.6%51.4%20.9%23.0%1.0%
202514,3554.6%49.8%21.1%23.0%1.4%
202610,0476.0%51.4%19.0%22.3%1.4%
22% of Theft Calls End “Unable to Locate,” Up From 7%Report-taken outcomes moved from 70% of calls in 2016 to 51% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Theft: 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 theft 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: 32.7 min2010: 24.1 min2011: 27.2 min2012: 36.1 min2013: 39.1 min2014: 62.4 min2015: 61.2 min2016: 62.6 min2017: 63.7 min2018: 74.6 min2019: 60.1 min2020: 54.0 min2021: 73.3 min2022: 68.4 min2023: 85.1 min2024: 109.1 min2025: 100.6 min2026: 100.7 min2009: 37.1 min2010: 28.6 min2011: 33.4 min2012: 43.8 min2013: 46.4 min2014: 71.4 min2015: 69.7 min2016: 71.6 min2017: 73.0 min2018: 84.9 min2019: 70.5 min2020: 62.4 min2021: 82.0 min2022: 75.9 min2023: 92.7 min2024: 116.5 min2025: 107.9 min2026: 106.6 min2009n=16,2892011n=18,5442013n=21,3502015n=21,4822017n=20,1322019n=15,2282021n=12,8992023n=12,5422025n=13,0072026n=8,882
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
200916,28932.7 min37.1 min
201022,59624.1 min28.6 min
201118,54427.2 min33.4 min
201219,62936.1 min43.8 min
201321,35039.1 min46.4 min
201423,17962.4 min71.4 min
201521,48261.2 min69.7 min
201620,96362.6 min71.6 min
201720,13263.7 min73.0 min
201819,46374.6 min84.9 min
201915,22860.1 min70.5 min
202011,77254.0 min62.4 min
202112,89973.3 min82.0 min
202211,80068.4 min75.9 min
202312,54285.1 min92.7 min
202412,827109.1 min116.5 min
202513,007100.6 min107.9 min
20268,882100.7 min106.6 min
The Average Call Waits 107 Minutes for an Officer to ArriveDespite a 41% drop in calls between 2016 and 2025, average response time has increased 49% in the past 10 years, from 72 minutes in 2016 to 107 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.

Theft: 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 theft 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: 3.2%2009 · 0–5 min: 18.8%2009 · 5–30 min: 41.0%2009 · 30–60 min: 19.7%2009 · 1–4 hr: 16.2%2009 · 4–8 hr: 1.0%2009 · Over 8 hr: 0.1%2010 · No recorded response: 2.7%2010 · 0–5 min: 25.5%2010 · 5–30 min: 44.2%2010 · 30–60 min: 15.5%2010 · 1–4 hr: 11.4%2010 · 4–8 hr: 0.5%2010 · Over 8 hr: 0.0%2011 · No recorded response: 3.7%2011 · 0–5 min: 22.2%2011 · 5–30 min: 41.7%2011 · 30–60 min: 16.2%2011 · 1–4 hr: 15.4%2011 · 4–8 hr: 0.9%2011 · Over 8 hr: 0.0%2012 · No recorded response: 3.7%2012 · 0–5 min: 18.7%2012 · 5–30 min: 38.1%2012 · 30–60 min: 17.0%2012 · 1–4 hr: 20.7%2012 · 4–8 hr: 1.7%2012 · Over 8 hr: 0.2%2013 · No recorded response: 3.6%2013 · 0–5 min: 17.9%2013 · 5–30 min: 37.4%2013 · 30–60 min: 16.2%2013 · 1–4 hr: 22.9%2013 · 4–8 hr: 1.9%2013 · Over 8 hr: 0.1%2014 · No recorded response: 4.1%2014 · 0–5 min: 10.9%2014 · 5–30 min: 34.1%2014 · 30–60 min: 15.9%2014 · 1–4 hr: 29.0%2014 · 4–8 hr: 5.5%2014 · Over 8 hr: 0.6%2015 · No recorded response: 4.1%2015 · 0–5 min: 14.4%2015 · 5–30 min: 32.7%2015 · 30–60 min: 15.3%2015 · 1–4 hr: 27.5%2015 · 4–8 hr: 5.2%2015 · Over 8 hr: 0.9%2016 · No recorded response: 3.8%2016 · 0–5 min: 14.4%2016 · 5–30 min: 34.2%2016 · 30–60 min: 14.9%2016 · 1–4 hr: 25.9%2016 · 4–8 hr: 5.8%2016 · Over 8 hr: 1.0%2017 · No recorded response: 4.0%2017 · 0–5 min: 12.3%2017 · 5–30 min: 34.7%2017 · 30–60 min: 15.2%2017 · 1–4 hr: 27.2%2017 · 4–8 hr: 5.3%2017 · Over 8 hr: 1.2%2018 · No recorded response: 4.8%2018 · 0–5 min: 9.3%2018 · 5–30 min: 30.2%2018 · 30–60 min: 15.6%2018 · 1–4 hr: 31.5%2018 · 4–8 hr: 7.6%2018 · Over 8 hr: 1.0%2019 · No recorded response: 5.3%2019 · 0–5 min: 11.3%2019 · 5–30 min: 33.4%2019 · 30–60 min: 15.4%2019 · 1–4 hr: 28.8%2019 · 4–8 hr: 5.1%2019 · Over 8 hr: 0.7%2020 · No recorded response: 5.5%2020 · 0–5 min: 14.3%2020 · 5–30 min: 34.8%2020 · 30–60 min: 14.6%2020 · 1–4 hr: 26.6%2020 · 4–8 hr: 3.6%2020 · Over 8 hr: 0.6%2021 · No recorded response: 7.8%2021 · 0–5 min: 11.1%2021 · 5–30 min: 32.2%2021 · 30–60 min: 14.3%2021 · 1–4 hr: 27.3%2021 · 4–8 hr: 5.8%2021 · Over 8 hr: 1.4%2022 · No recorded response: 9.0%2022 · 0–5 min: 13.0%2022 · 5–30 min: 31.9%2022 · 30–60 min: 14.4%2022 · 1–4 hr: 25.0%2022 · 4–8 hr: 4.9%2022 · Over 8 hr: 1.7%2023 · No recorded response: 11.3%2023 · 0–5 min: 12.9%2023 · 5–30 min: 28.8%2023 · 30–60 min: 13.4%2023 · 1–4 hr: 24.5%2023 · 4–8 hr: 6.2%2023 · Over 8 hr: 2.8%2024 · No recorded response: 10.7%2024 · 0–5 min: 9.8%2024 · 5–30 min: 24.9%2024 · 30–60 min: 13.5%2024 · 1–4 hr: 28.1%2024 · 4–8 hr: 9.3%2024 · Over 8 hr: 3.7%2025 · No recorded response: 6.1%2025 · 0–5 min: 13.7%2025 · 5–30 min: 26.9%2025 · 30–60 min: 13.9%2025 · 1–4 hr: 27.5%2025 · 4–8 hr: 8.4%2025 · Over 8 hr: 3.4%2026 · No recorded response: 5.8%2026 · 0–5 min: 11.6%2026 · 5–30 min: 29.2%2026 · 30–60 min: 14.2%2026 · 1–4 hr: 26.8%2026 · 4–8 hr: 8.8%2026 · Over 8 hr: 3.6%2009n=16,2892011n=18,5442013n=21,3502015n=21,4822017n=20,1322019n=15,2282021n=12,8992023n=12,5422025n=13,0072026n=8,882
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
200916,2893.2%18.8%41.0%19.7%16.2%1.0%0.1%
201022,5962.7%25.5%44.2%15.5%11.4%0.5%0.0%
201118,5443.7%22.2%41.7%16.2%15.4%0.9%0.0%
201219,6293.7%18.7%38.1%17.0%20.7%1.7%0.2%
201321,3503.6%17.9%37.4%16.2%22.9%1.9%0.1%
201423,1794.1%10.9%34.1%15.9%29.0%5.5%0.6%
201521,4824.1%14.4%32.7%15.3%27.5%5.2%0.9%
201620,9633.8%14.4%34.2%14.9%25.9%5.8%1.0%
201720,1324.0%12.3%34.7%15.2%27.2%5.3%1.2%
201819,4634.8%9.3%30.2%15.6%31.5%7.6%1.0%
201915,2285.3%11.3%33.4%15.4%28.8%5.1%0.7%
202011,7725.5%14.3%34.8%14.6%26.6%3.6%0.6%
202112,8997.8%11.1%32.2%14.3%27.3%5.8%1.4%
202211,8009.0%13.0%31.9%14.4%25.0%4.9%1.7%
202312,54211.3%12.9%28.8%13.4%24.5%6.2%2.8%
202412,82710.7%9.8%24.9%13.5%28.1%9.3%3.7%
202513,0076.1%13.7%26.9%13.9%27.5%8.4%3.4%
20268,8825.8%11.6%29.2%14.2%26.8%8.8%3.6%
The Average Call Waits 101 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 101 minutes in 2026, about 1.6 times what it was in 2016. 39% of calls took more than an hour to get a response in 2026, compared with 33% 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.