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

Burglary

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

Burglary: 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 (9% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
06,00012,0002009: 4,946 burglary calls logged in CAD2010: 8,044 burglary calls logged in CAD2011: 8,578 burglary calls logged in CAD2012: 8,221 burglary calls logged in CAD2013: 8,819 burglary calls logged in CAD2014: 8,665 burglary calls logged in CAD2015: 9,111 burglary calls logged in CAD2016: 8,704 burglary calls logged in CAD2017: 9,042 burglary calls logged in CAD2018: 9,481 burglary calls logged in CAD2019: 9,135 burglary calls logged in CAD2020: 9,542 burglary calls logged in CAD2021: 7,454 burglary calls logged in CAD2022: 6,499 burglary calls logged in CAD2023: 6,188 burglary calls logged in CAD2024: 5,443 burglary calls logged in CAD2025: 4,726 burglary calls logged in CAD2026: 3,274 burglary calls logged in CAD2009n=4,9462011n=8,5782013n=8,8192015n=9,1112017n=9,0422019n=9,1352021n=7,4542023n=6,1882025n=4,7262026n=3,274
burglary calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodBurglary calls logged in CAD
20094,946
20108,044
20118,578
20128,221
20138,819
20148,665
20159,111
20168,704
20179,042
20189,481
20199,135
20209,542
20217,454
20226,499
20236,188
20245,443
20254,726
20263,274
Burglary Calls Are Down 50% From Their 2020 PeakSeattle Police logged 9,542 burglary calls in 2020 and 4,726 in 2025, the most recent full year.

Burglary: 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: 84.8%2009 · Resolved on scene: 7.2%2009 · Unable to locate: 1.9%2009 · Other (unfounded / cancelled): 3.2%2010 · Arrest / citation: 3.4%2010 · Report taken, no arrest: 83.9%2010 · Resolved on scene: 7.8%2010 · Unable to locate: 2.2%2010 · Other (unfounded / cancelled): 2.7%2011 · Arrest / citation: 3.3%2011 · Report taken, no arrest: 86.1%2011 · Resolved on scene: 6.9%2011 · Unable to locate: 1.8%2011 · Other (unfounded / cancelled): 1.9%2012 · Arrest / citation: 3.2%2012 · Report taken, no arrest: 85.5%2012 · Resolved on scene: 7.1%2012 · Unable to locate: 2.2%2012 · Other (unfounded / cancelled): 2.0%2013 · Arrest / citation: 2.7%2013 · Report taken, no arrest: 87.9%2013 · Resolved on scene: 5.5%2013 · Unable to locate: 2.1%2013 · Other (unfounded / cancelled): 1.8%2014 · Arrest / citation: 3.0%2014 · Report taken, no arrest: 87.3%2014 · Resolved on scene: 5.1%2014 · Unable to locate: 2.6%2014 · Other (unfounded / cancelled): 2.1%2015 · Arrest / citation: 2.8%2015 · Report taken, no arrest: 87.4%2015 · Resolved on scene: 4.8%2015 · Unable to locate: 2.8%2015 · Other (unfounded / cancelled): 2.2%2016 · Arrest / citation: 3.8%2016 · Report taken, no arrest: 87.0%2016 · Resolved on scene: 5.0%2016 · Unable to locate: 2.4%2016 · Other (unfounded / cancelled): 1.8%2017 · Arrest / citation: 4.4%2017 · Report taken, no arrest: 85.9%2017 · Resolved on scene: 5.2%2017 · Unable to locate: 2.4%2017 · Other (unfounded / cancelled): 2.1%2018 · Arrest / citation: 4.5%2018 · Report taken, no arrest: 85.3%2018 · Resolved on scene: 4.6%2018 · Unable to locate: 3.3%2018 · Other (unfounded / cancelled): 2.3%2019 · Arrest / citation: 5.0%2019 · Report taken, no arrest: 84.5%2019 · Resolved on scene: 4.5%2019 · Unable to locate: 3.4%2019 · Other (unfounded / cancelled): 2.5%2020 · Arrest / citation: 6.7%2020 · Report taken, no arrest: 82.8%2020 · Resolved on scene: 5.8%2020 · Unable to locate: 3.2%2020 · Other (unfounded / cancelled): 1.5%2021 · Arrest / citation: 10.3%2021 · Report taken, no arrest: 77.7%2021 · Resolved on scene: 5.8%2021 · Unable to locate: 4.7%2021 · Other (unfounded / cancelled): 1.4%2022 · Arrest / citation: 10.4%2022 · Report taken, no arrest: 77.2%2022 · Resolved on scene: 6.2%2022 · Unable to locate: 5.2%2022 · Other (unfounded / cancelled): 1.0%2023 · Arrest / citation: 10.8%2023 · Report taken, no arrest: 68.9%2023 · Resolved on scene: 11.7%2023 · Unable to locate: 7.2%2023 · Other (unfounded / cancelled): 1.4%2024 · Arrest / citation: 9.9%2024 · Report taken, no arrest: 74.8%2024 · Resolved on scene: 6.6%2024 · Unable to locate: 7.5%2024 · Other (unfounded / cancelled): 1.2%2025 · Arrest / citation: 10.3%2025 · Report taken, no arrest: 71.2%2025 · Resolved on scene: 8.7%2025 · Unable to locate: 8.3%2025 · Other (unfounded / cancelled): 1.4%2026 · Arrest / citation: 11.7%2026 · Report taken, no arrest: 70.2%2026 · Resolved on scene: 8.2%2026 · Unable to locate: 8.8%2026 · Other (unfounded / cancelled): 1.2%2009n=4,9462011n=8,5782013n=8,8192015n=9,1112017n=9,0422019n=9,1352021n=7,4542023n=6,1882025n=4,7262026n=3,274
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)
20094,9462.9%84.8%7.2%1.9%3.2%
20108,0443.4%83.9%7.8%2.2%2.7%
20118,5783.3%86.1%6.9%1.8%1.9%
20128,2213.2%85.5%7.1%2.2%2.0%
20138,8192.7%87.9%5.5%2.1%1.8%
20148,6653.0%87.3%5.1%2.6%2.1%
20159,1112.8%87.4%4.8%2.8%2.2%
20168,7043.8%87.0%5.0%2.4%1.8%
20179,0424.4%85.9%5.2%2.4%2.1%
20189,4814.5%85.3%4.6%3.3%2.3%
20199,1355.0%84.5%4.5%3.4%2.5%
20209,5426.7%82.8%5.8%3.2%1.5%
20217,45410.3%77.7%5.8%4.7%1.4%
20226,49910.4%77.2%6.2%5.2%1.0%
20236,18810.8%68.9%11.7%7.2%1.4%
20245,4439.9%74.8%6.6%7.5%1.2%
20254,72610.3%71.2%8.7%8.3%1.4%
20263,27411.7%70.2%8.2%8.8%1.2%
9% of Burglary Calls End “Unable to Locate,” Up From 2%Report-taken outcomes moved from 87% of calls in 2016 to 70% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Burglary: 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 9% of burglary 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: 38.9 min2010: 30.5 min2011: 33.4 min2012: 42.3 min2013: 45.9 min2014: 49.0 min2015: 65.1 min2016: 59.4 min2017: 59.7 min2018: 72.6 min2019: 70.2 min2020: 57.4 min2021: 66.3 min2022: 56.7 min2023: 97.7 min2024: 94.9 min2025: 84.6 min2026: 80.6 min2009: 50.8 min2010: 41.2 min2011: 46.8 min2012: 56.7 min2013: 60.1 min2014: 63.5 min2015: 78.9 min2016: 71.6 min2017: 75.0 min2018: 87.9 min2019: 86.2 min2020: 66.0 min2021: 73.5 min2022: 65.1 min2023: 100.1 min2024: 102.2 min2025: 91.6 min2026: 89.0 min2009n=4,5402011n=7,4852013n=8,0512015n=8,3932017n=8,2022019n=8,4032021n=6,9142023n=5,7512025n=4,3852026n=3,036
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
20094,54038.9 min50.8 min
20107,12430.5 min41.2 min
20117,48533.4 min46.8 min
20127,33242.3 min56.7 min
20138,05145.9 min60.1 min
20147,98349.0 min63.5 min
20158,39365.1 min78.9 min
20167,98759.4 min71.6 min
20178,20259.7 min75.0 min
20188,66372.6 min87.9 min
20198,40370.2 min86.2 min
20208,91257.4 min66.0 min
20216,91466.3 min73.5 min
20225,94156.7 min65.1 min
20235,75197.7 min100.1 min
20245,02794.9 min102.2 min
20254,38584.6 min91.6 min
20263,03680.6 min89.0 min
The Average Call Waits 89 Minutes for an Officer to ArriveDespite a 46% drop in calls between 2016 and 2025, average response time has increased 24% in the past 10 years, from 72 minutes in 2016 to 89 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.

Burglary: 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 9% of burglary 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.7%2009 · 0–5 min: 14.3%2009 · 5–30 min: 38.5%2009 · 30–60 min: 16.5%2009 · 1–4 hr: 24.6%2009 · 4–8 hr: 2.2%2009 · Over 8 hr: 0.2%2010 · No recorded response: 3.9%2010 · 0–5 min: 17.4%2010 · 5–30 min: 41.6%2010 · 30–60 min: 15.6%2010 · 1–4 hr: 20.2%2010 · 4–8 hr: 1.3%2010 · Over 8 hr: 0.0%2011 · No recorded response: 3.7%2011 · 0–5 min: 13.9%2011 · 5–30 min: 41.1%2011 · 30–60 min: 17.1%2011 · 1–4 hr: 22.3%2011 · 4–8 hr: 1.7%2011 · Over 8 hr: 0.1%2012 · No recorded response: 3.7%2012 · 0–5 min: 11.7%2012 · 5–30 min: 38.5%2012 · 30–60 min: 16.7%2012 · 1–4 hr: 26.5%2012 · 4–8 hr: 2.7%2012 · Over 8 hr: 0.2%2013 · No recorded response: 3.8%2013 · 0–5 min: 10.9%2013 · 5–30 min: 38.7%2013 · 30–60 min: 15.8%2013 · 1–4 hr: 26.9%2013 · 4–8 hr: 3.6%2013 · Over 8 hr: 0.2%2014 · No recorded response: 3.4%2014 · 0–5 min: 9.4%2014 · 5–30 min: 37.9%2014 · 30–60 min: 16.5%2014 · 1–4 hr: 28.6%2014 · 4–8 hr: 3.9%2014 · Over 8 hr: 0.3%2015 · No recorded response: 3.6%2015 · 0–5 min: 8.4%2015 · 5–30 min: 33.7%2015 · 30–60 min: 15.3%2015 · 1–4 hr: 32.2%2015 · 4–8 hr: 6.1%2015 · Over 8 hr: 0.6%2016 · No recorded response: 3.0%2016 · 0–5 min: 8.5%2016 · 5–30 min: 35.4%2016 · 30–60 min: 16.0%2016 · 1–4 hr: 31.8%2016 · 4–8 hr: 5.1%2016 · Over 8 hr: 0.2%2017 · No recorded response: 3.5%2017 · 0–5 min: 8.1%2017 · 5–30 min: 33.5%2017 · 30–60 min: 16.5%2017 · 1–4 hr: 32.8%2017 · 4–8 hr: 5.4%2017 · Over 8 hr: 0.3%2018 · No recorded response: 3.8%2018 · 0–5 min: 7.7%2018 · 5–30 min: 31.5%2018 · 30–60 min: 15.4%2018 · 1–4 hr: 32.7%2018 · 4–8 hr: 8.2%2018 · Over 8 hr: 0.8%2019 · No recorded response: 4.4%2019 · 0–5 min: 6.8%2019 · 5–30 min: 32.5%2019 · 30–60 min: 15.3%2019 · 1–4 hr: 33.0%2019 · 4–8 hr: 6.8%2019 · Over 8 hr: 1.2%2020 · No recorded response: 2.5%2020 · 0–5 min: 16.6%2020 · 5–30 min: 33.7%2020 · 30–60 min: 13.8%2020 · 1–4 hr: 28.0%2020 · 4–8 hr: 5.0%2020 · Over 8 hr: 0.3%2021 · No recorded response: 3.4%2021 · 0–5 min: 16.3%2021 · 5–30 min: 37.1%2021 · 30–60 min: 12.2%2021 · 1–4 hr: 23.3%2021 · 4–8 hr: 6.3%2021 · Over 8 hr: 1.4%2022 · No recorded response: 3.2%2022 · 0–5 min: 18.8%2022 · 5–30 min: 39.2%2022 · 30–60 min: 11.8%2022 · 1–4 hr: 20.7%2022 · 4–8 hr: 4.7%2022 · Over 8 hr: 1.6%2023 · No recorded response: 7.0%2023 · 0–5 min: 18.5%2023 · 5–30 min: 34.5%2023 · 30–60 min: 10.1%2023 · 1–4 hr: 18.8%2023 · 4–8 hr: 5.7%2023 · Over 8 hr: 5.3%2024 · No recorded response: 4.7%2024 · 0–5 min: 14.4%2024 · 5–30 min: 34.9%2024 · 30–60 min: 11.0%2024 · 1–4 hr: 22.6%2024 · 4–8 hr: 8.2%2024 · Over 8 hr: 4.1%2025 · No recorded response: 2.1%2025 · 0–5 min: 18.6%2025 · 5–30 min: 34.7%2025 · 30–60 min: 11.0%2025 · 1–4 hr: 22.9%2025 · 4–8 hr: 7.5%2025 · Over 8 hr: 3.4%2026 · No recorded response: 1.8%2026 · 0–5 min: 18.7%2026 · 5–30 min: 35.9%2026 · 30–60 min: 12.3%2026 · 1–4 hr: 19.6%2026 · 4–8 hr: 8.1%2026 · Over 8 hr: 3.5%2009n=4,5402011n=7,4852013n=8,0512015n=8,3932017n=8,2022019n=8,4032021n=6,9142023n=5,7512025n=4,3852026n=3,036
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
20094,5403.7%14.3%38.5%16.5%24.6%2.2%0.2%
20107,1243.9%17.4%41.6%15.6%20.2%1.3%0.0%
20117,4853.7%13.9%41.1%17.1%22.3%1.7%0.1%
20127,3323.7%11.7%38.5%16.7%26.5%2.7%0.2%
20138,0513.8%10.9%38.7%15.8%26.9%3.6%0.2%
20147,9833.4%9.4%37.9%16.5%28.6%3.9%0.3%
20158,3933.6%8.4%33.7%15.3%32.2%6.1%0.6%
20167,9873.0%8.5%35.4%16.0%31.8%5.1%0.2%
20178,2023.5%8.1%33.5%16.5%32.8%5.4%0.3%
20188,6633.8%7.7%31.5%15.4%32.7%8.2%0.8%
20198,4034.4%6.8%32.5%15.3%33.0%6.8%1.2%
20208,9122.5%16.6%33.7%13.8%28.0%5.0%0.3%
20216,9143.4%16.3%37.1%12.2%23.3%6.3%1.4%
20225,9413.2%18.8%39.2%11.8%20.7%4.7%1.6%
20235,7517.0%18.5%34.5%10.1%18.8%5.7%5.3%
20245,0274.7%14.4%34.9%11.0%22.6%8.2%4.1%
20254,3852.1%18.6%34.7%11.0%22.9%7.5%3.4%
20263,0361.8%18.7%35.9%12.3%19.6%8.1%3.5%
The Average Call Waits 81 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 81 minutes in 2026, up from 59 minutes in 2016. 31% of calls took more than an hour to get a response in 2026, compared with 37% 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.