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

Mischief & Nuisance

Mischief & Nuisance calls over time: volume, outcomes, and response speed

Mischief & Nuisance: 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 (35% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
06,00012,0002009: 3,678 mischief & nuisance calls logged in CAD2010: 6,340 mischief & nuisance calls logged in CAD2011: 6,844 mischief & nuisance calls logged in CAD2012: 6,592 mischief & nuisance calls logged in CAD2013: 6,568 mischief & nuisance calls logged in CAD2014: 7,901 mischief & nuisance calls logged in CAD2015: 9,815 mischief & nuisance calls logged in CAD2016: 9,933 mischief & nuisance calls logged in CAD2017: 8,957 mischief & nuisance calls logged in CAD2018: 9,947 mischief & nuisance calls logged in CAD2019: 9,378 mischief & nuisance calls logged in CAD2020: 4,499 mischief & nuisance calls logged in CAD2021: 3,584 mischief & nuisance calls logged in CAD2022: 4,588 mischief & nuisance calls logged in CAD2023: 5,135 mischief & nuisance calls logged in CAD2024: 5,163 mischief & nuisance calls logged in CAD2025: 4,383 mischief & nuisance calls logged in CAD2026: 3,073 mischief & nuisance calls logged in CAD2009n=3,6782011n=6,8442013n=6,5682015n=9,8152017n=8,9572019n=9,3782021n=3,5842023n=5,1352025n=4,3832026n=3,073
mischief & nuisance calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodMischief & nuisance calls logged in CAD
20093,678
20106,340
20116,844
20126,592
20136,568
20147,901
20159,815
20169,933
20178,957
20189,947
20199,378
20204,499
20213,584
20224,588
20235,135
20245,163
20254,383
20263,073
Mischief & Nuisance Calls Are Down 56% From Their 2018 PeakSeattle Police logged 9,947 mischief & nuisance calls in 2018 and 4,383 in 2025, the most recent full year.

Mischief & Nuisance: 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: 1.5%2009 · Report taken, no arrest: 2.0%2009 · Resolved on scene: 83.5%2009 · Unable to locate: 12.2%2009 · Other (unfounded / cancelled): 0.8%2010 · Arrest / citation: 2.2%2010 · Report taken, no arrest: 3.8%2010 · Resolved on scene: 83.0%2010 · Unable to locate: 10.4%2010 · Other (unfounded / cancelled): 0.7%2011 · Arrest / citation: 1.7%2011 · Report taken, no arrest: 3.0%2011 · Resolved on scene: 83.8%2011 · Unable to locate: 10.8%2011 · Other (unfounded / cancelled): 0.7%2012 · Arrest / citation: 0.9%2012 · Report taken, no arrest: 2.7%2012 · Resolved on scene: 82.4%2012 · Unable to locate: 13.3%2012 · Other (unfounded / cancelled): 0.8%2013 · Arrest / citation: 1.1%2013 · Report taken, no arrest: 2.2%2013 · Resolved on scene: 80.5%2013 · Unable to locate: 15.0%2013 · Other (unfounded / cancelled): 1.2%2014 · Arrest / citation: 2.2%2014 · Report taken, no arrest: 7.0%2014 · Resolved on scene: 75.8%2014 · Unable to locate: 14.2%2014 · Other (unfounded / cancelled): 0.8%2015 · Arrest / citation: 8.4%2015 · Report taken, no arrest: 4.8%2015 · Resolved on scene: 71.1%2015 · Unable to locate: 14.8%2015 · Other (unfounded / cancelled): 1.0%2016 · Arrest / citation: 4.6%2016 · Report taken, no arrest: 3.3%2016 · Resolved on scene: 77.2%2016 · Unable to locate: 13.0%2016 · Other (unfounded / cancelled): 1.9%2017 · Arrest / citation: 3.8%2017 · Report taken, no arrest: 5.0%2017 · Resolved on scene: 77.4%2017 · Unable to locate: 12.5%2017 · Other (unfounded / cancelled): 1.4%2018 · Arrest / citation: 2.8%2018 · Report taken, no arrest: 3.1%2018 · Resolved on scene: 75.3%2018 · Unable to locate: 16.8%2018 · Other (unfounded / cancelled): 2.0%2019 · Arrest / citation: 2.1%2019 · Report taken, no arrest: 6.0%2019 · Resolved on scene: 74.4%2019 · Unable to locate: 16.2%2019 · Other (unfounded / cancelled): 1.3%2020 · Arrest / citation: 1.4%2020 · Report taken, no arrest: 4.9%2020 · Resolved on scene: 79.8%2020 · Unable to locate: 12.8%2020 · Other (unfounded / cancelled): 1.1%2021 · Arrest / citation: 0.6%2021 · Report taken, no arrest: 2.5%2021 · Resolved on scene: 74.4%2021 · Unable to locate: 20.7%2021 · Other (unfounded / cancelled): 1.8%2022 · Arrest / citation: 0.2%2022 · Report taken, no arrest: 1.8%2022 · Resolved on scene: 71.8%2022 · Unable to locate: 25.1%2022 · Other (unfounded / cancelled): 1.1%2023 · Arrest / citation: 0.1%2023 · Report taken, no arrest: 1.6%2023 · Resolved on scene: 67.0%2023 · Unable to locate: 29.8%2023 · Other (unfounded / cancelled): 1.6%2024 · Arrest / citation: 0.2%2024 · Report taken, no arrest: 2.1%2024 · Resolved on scene: 60.1%2024 · Unable to locate: 36.2%2024 · Other (unfounded / cancelled): 1.4%2025 · Arrest / citation: 0.3%2025 · Report taken, no arrest: 1.8%2025 · Resolved on scene: 56.1%2025 · Unable to locate: 40.1%2025 · Other (unfounded / cancelled): 1.7%2026 · Arrest / citation: 0.2%2026 · Report taken, no arrest: 2.1%2026 · Resolved on scene: 56.1%2026 · Unable to locate: 39.4%2026 · Other (unfounded / cancelled): 2.1%2009n=3,6782011n=6,8442013n=6,5682015n=9,8152017n=8,9572019n=9,3782021n=3,5842023n=5,1352025n=4,3832026n=3,073
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)
20093,6781.5%2.0%83.5%12.2%0.8%
20106,3402.2%3.8%83.0%10.4%0.7%
20116,8441.7%3.0%83.8%10.8%0.7%
20126,5920.9%2.7%82.4%13.3%0.8%
20136,5681.1%2.2%80.5%15.0%1.2%
20147,9012.2%7.0%75.8%14.2%0.8%
20159,8158.4%4.8%71.1%14.8%1.0%
20169,9334.6%3.3%77.2%13.0%1.9%
20178,9573.8%5.0%77.4%12.5%1.4%
20189,9472.8%3.1%75.3%16.8%2.0%
20199,3782.1%6.0%74.4%16.2%1.3%
20204,4991.4%4.9%79.8%12.8%1.1%
20213,5840.6%2.5%74.4%20.7%1.8%
20224,5880.2%1.8%71.8%25.1%1.1%
20235,1350.1%1.6%67.0%29.8%1.6%
20245,1630.2%2.1%60.1%36.2%1.4%
20254,3830.3%1.8%56.1%40.1%1.7%
20263,0730.2%2.1%56.1%39.4%2.1%
39% of Mischief & Nuisance Calls End “Unable to Locate,” Up From 13%Report-taken outcomes moved from 3% of calls in 2016 to 2% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Mischief & Nuisance: 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 35% of mischief & nuisance 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 min100 min200 min2009: 30.7 min2010: 24.2 min2011: 23.8 min2012: 30.9 min2013: 33.1 min2014: 39.1 min2015: 61.4 min2016: 52.1 min2017: 53.1 min2018: 70.0 min2019: 55.9 min2020: 42.3 min2021: 62.6 min2022: 71.7 min2023: 92.4 min2024: 136.3 min2025: 135.5 min2026: 129.6 min2009: 36.6 min2010: 29.5 min2011: 30.8 min2012: 36.8 min2013: 39.2 min2014: 46.3 min2015: 68.1 min2016: 60.3 min2017: 61.4 min2018: 77.6 min2019: 63.6 min2020: 49.8 min2021: 70.2 min2022: 78.1 min2023: 99.3 min2024: 141.8 min2025: 143.8 min2026: 134.8 min2009n=2,2012011n=3,5132013n=4,8962015n=6,1252017n=5,0432019n=5,2822021n=2,4722023n=3,9162025n=3,9232026n=2,831
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
20092,20130.7 min36.6 min
20103,24424.2 min29.5 min
20113,51323.8 min30.8 min
20124,21630.9 min36.8 min
20134,89633.1 min39.2 min
20145,34039.1 min46.3 min
20156,12561.4 min68.1 min
20165,84752.1 min60.3 min
20175,04353.1 min61.4 min
20186,73970.0 min77.6 min
20195,28255.9 min63.6 min
20202,43842.3 min49.8 min
20212,47262.6 min70.2 min
20223,24671.7 min78.1 min
20233,91692.4 min99.3 min
20244,220136.3 min141.8 min
20253,923135.5 min143.8 min
20262,831129.6 min134.8 min
The Average Call Waits 135 Minutes for an Officer to ArriveDespite a 56% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 60 minutes in 2016 to 135 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.

Mischief & Nuisance: 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 35% of mischief & nuisance 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: 9.1%2009 · 0–5 min: 11.9%2009 · 5–30 min: 49.5%2009 · 30–60 min: 14.1%2009 · 1–4 hr: 14.5%2009 · 4–8 hr: 0.8%2009 · Over 8 hr: 0.1%2010 · No recorded response: 8.7%2010 · 0–5 min: 14.9%2010 · 5–30 min: 50.3%2010 · 30–60 min: 13.7%2010 · 1–4 hr: 12.0%2010 · 4–8 hr: 0.4%2011 · No recorded response: 8.8%2011 · 0–5 min: 14.4%2011 · 5–30 min: 50.5%2011 · 30–60 min: 13.7%2011 · 1–4 hr: 12.2%2011 · 4–8 hr: 0.5%2011 · Over 8 hr: 0.0%2012 · No recorded response: 8.9%2012 · 0–5 min: 12.8%2012 · 5–30 min: 47.1%2012 · 30–60 min: 15.0%2012 · 1–4 hr: 15.1%2012 · 4–8 hr: 1.0%2012 · Over 8 hr: 0.1%2013 · No recorded response: 9.3%2013 · 0–5 min: 11.6%2013 · 5–30 min: 45.6%2013 · 30–60 min: 15.3%2013 · 1–4 hr: 17.0%2013 · 4–8 hr: 1.1%2013 · Over 8 hr: 0.1%2014 · No recorded response: 8.3%2014 · 0–5 min: 10.7%2014 · 5–30 min: 44.3%2014 · 30–60 min: 15.2%2014 · 1–4 hr: 19.3%2014 · 4–8 hr: 2.1%2014 · Over 8 hr: 0.2%2015 · No recorded response: 7.8%2015 · 0–5 min: 9.2%2015 · 5–30 min: 38.0%2015 · 30–60 min: 15.7%2015 · 1–4 hr: 23.7%2015 · 4–8 hr: 4.2%2015 · Over 8 hr: 1.3%2016 · No recorded response: 8.5%2016 · 0–5 min: 9.5%2016 · 5–30 min: 40.0%2016 · 30–60 min: 15.3%2016 · 1–4 hr: 22.0%2016 · 4–8 hr: 4.1%2016 · Over 8 hr: 0.6%2017 · No recorded response: 7.3%2017 · 0–5 min: 8.8%2017 · 5–30 min: 39.3%2017 · 30–60 min: 15.5%2017 · 1–4 hr: 25.2%2017 · 4–8 hr: 3.5%2017 · Over 8 hr: 0.5%2018 · No recorded response: 7.8%2018 · 0–5 min: 8.0%2018 · 5–30 min: 34.9%2018 · 30–60 min: 15.2%2018 · 1–4 hr: 26.9%2018 · 4–8 hr: 6.1%2018 · Over 8 hr: 1.1%2019 · No recorded response: 9.7%2019 · 0–5 min: 8.1%2019 · 5–30 min: 37.7%2019 · 30–60 min: 15.6%2019 · 1–4 hr: 24.5%2019 · 4–8 hr: 3.9%2019 · Over 8 hr: 0.5%2020 · No recorded response: 8.7%2020 · 0–5 min: 11.3%2020 · 5–30 min: 43.5%2020 · 30–60 min: 13.8%2020 · 1–4 hr: 20.1%2020 · 4–8 hr: 2.3%2020 · Over 8 hr: 0.3%2021 · No recorded response: 11.8%2021 · 0–5 min: 6.6%2021 · 5–30 min: 37.4%2021 · 30–60 min: 14.8%2021 · 1–4 hr: 23.7%2021 · 4–8 hr: 4.7%2021 · Over 8 hr: 1.1%2022 · No recorded response: 15.3%2022 · 0–5 min: 8.8%2022 · 5–30 min: 31.8%2022 · 30–60 min: 13.0%2022 · 1–4 hr: 24.4%2022 · 4–8 hr: 5.3%2022 · Over 8 hr: 1.4%2023 · No recorded response: 15.6%2023 · 0–5 min: 6.2%2023 · 5–30 min: 29.4%2023 · 30–60 min: 12.6%2023 · 1–4 hr: 26.8%2023 · 4–8 hr: 7.0%2023 · Over 8 hr: 2.5%2024 · No recorded response: 19.1%2024 · 0–5 min: 2.8%2024 · 5–30 min: 19.8%2024 · 30–60 min: 12.5%2024 · 1–4 hr: 30.4%2024 · 4–8 hr: 11.2%2024 · Over 8 hr: 4.2%2025 · No recorded response: 14.5%2025 · 0–5 min: 3.5%2025 · 5–30 min: 20.4%2025 · 30–60 min: 13.8%2025 · 1–4 hr: 32.5%2025 · 4–8 hr: 10.3%2025 · Over 8 hr: 5.1%2026 · No recorded response: 13.9%2026 · 0–5 min: 4.3%2026 · 5–30 min: 22.4%2026 · 30–60 min: 13.8%2026 · 1–4 hr: 29.8%2026 · 4–8 hr: 11.4%2026 · Over 8 hr: 4.4%2009n=2,2012011n=3,5132013n=4,8962015n=6,1252017n=5,0432019n=5,2822021n=2,4722023n=3,9162025n=3,9232026n=2,831
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
20092,2019.1%11.9%49.5%14.1%14.5%0.8%0.1%
20103,2448.7%14.9%50.3%13.7%12.0%0.4%—
20113,5138.8%14.4%50.5%13.7%12.2%0.5%0.0%
20124,2168.9%12.8%47.1%15.0%15.1%1.0%0.1%
20134,8969.3%11.6%45.6%15.3%17.0%1.1%0.1%
20145,3408.3%10.7%44.3%15.2%19.3%2.1%0.2%
20156,1257.8%9.2%38.0%15.7%23.7%4.2%1.3%
20165,8478.5%9.5%40.0%15.3%22.0%4.1%0.6%
20175,0437.3%8.8%39.3%15.5%25.2%3.5%0.5%
20186,7397.8%8.0%34.9%15.2%26.9%6.1%1.1%
20195,2829.7%8.1%37.7%15.6%24.5%3.9%0.5%
20202,4388.7%11.3%43.5%13.8%20.1%2.3%0.3%
20212,47211.8%6.6%37.4%14.8%23.7%4.7%1.1%
20223,24615.3%8.8%31.8%13.0%24.4%5.3%1.4%
20233,91615.6%6.2%29.4%12.6%26.8%7.0%2.5%
20244,22019.1%2.8%19.8%12.5%30.4%11.2%4.2%
20253,92314.5%3.5%20.4%13.8%32.5%10.3%5.1%
20262,83113.9%4.3%22.4%13.8%29.8%11.4%4.4%
The Average Call Waits 130 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 130 minutes in 2026, more than double what it was in 2016. 46% of calls took more than an hour to get a response in 2026, compared with 27% 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.