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

Traffic

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

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

Swipe sideways to see the full chart →
050,000100,0002009: 47,508 traffic calls logged in CAD2010: 84,848 traffic calls logged in CAD2011: 68,109 traffic calls logged in CAD2012: 64,125 traffic calls logged in CAD2013: 62,713 traffic calls logged in CAD2014: 61,385 traffic calls logged in CAD2015: 67,442 traffic calls logged in CAD2016: 69,446 traffic calls logged in CAD2017: 70,328 traffic calls logged in CAD2018: 75,944 traffic calls logged in CAD2019: 83,194 traffic calls logged in CAD2020: 44,663 traffic calls logged in CAD2021: 41,583 traffic calls logged in CAD2022: 35,605 traffic calls logged in CAD2023: 39,729 traffic calls logged in CAD2024: 41,011 traffic calls logged in CAD2025: 52,038 traffic calls logged in CAD2026: 43,411 traffic calls logged in CAD2009n=47,5082011n=68,1092013n=62,7132015n=67,4422017n=70,3282019n=83,1942021n=41,5832023n=39,7292025n=52,0382026n=43,411
traffic calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodTraffic calls logged in CAD
200947,508
201084,848
201168,109
201264,125
201362,713
201461,385
201567,442
201669,446
201770,328
201875,944
201983,194
202044,663
202141,583
202235,605
202339,729
202441,011
202552,038
202643,411
Traffic Calls Are Down 39% From Their 2010 PeakSeattle Police logged 84,848 traffic calls in 2010 and 52,038 in 2025, the most recent full year.

Traffic: 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: 33.6%2009 · Report taken, no arrest: 29.1%2009 · Resolved on scene: 26.0%2009 · Unable to locate: 9.0%2009 · Other (unfounded / cancelled): 2.3%2010 · Arrest / citation: 32.2%2010 · Report taken, no arrest: 28.8%2010 · Resolved on scene: 28.7%2010 · Unable to locate: 8.3%2010 · Other (unfounded / cancelled): 2.0%2011 · Arrest / citation: 29.4%2011 · Report taken, no arrest: 29.4%2011 · Resolved on scene: 29.2%2011 · Unable to locate: 9.7%2011 · Other (unfounded / cancelled): 2.3%2012 · Arrest / citation: 26.6%2012 · Report taken, no arrest: 32.0%2012 · Resolved on scene: 28.7%2012 · Unable to locate: 10.3%2012 · Other (unfounded / cancelled): 2.5%2013 · Arrest / citation: 27.3%2013 · Report taken, no arrest: 30.7%2013 · Resolved on scene: 28.1%2013 · Unable to locate: 11.1%2013 · Other (unfounded / cancelled): 2.8%2014 · Arrest / citation: 27.0%2014 · Report taken, no arrest: 33.1%2014 · Resolved on scene: 24.5%2014 · Unable to locate: 13.0%2014 · Other (unfounded / cancelled): 2.3%2015 · Arrest / citation: 27.2%2015 · Report taken, no arrest: 32.8%2015 · Resolved on scene: 24.9%2015 · Unable to locate: 13.0%2015 · Other (unfounded / cancelled): 2.1%2016 · Arrest / citation: 28.7%2016 · Report taken, no arrest: 32.6%2016 · Resolved on scene: 24.8%2016 · Unable to locate: 11.8%2016 · Other (unfounded / cancelled): 2.1%2017 · Arrest / citation: 30.1%2017 · Report taken, no arrest: 32.4%2017 · Resolved on scene: 24.7%2017 · Unable to locate: 10.7%2017 · Other (unfounded / cancelled): 2.1%2018 · Arrest / citation: 34.2%2018 · Report taken, no arrest: 28.6%2018 · Resolved on scene: 23.6%2018 · Unable to locate: 11.4%2018 · Other (unfounded / cancelled): 2.1%2019 · Arrest / citation: 38.3%2019 · Report taken, no arrest: 26.3%2019 · Resolved on scene: 23.5%2019 · Unable to locate: 10.2%2019 · Other (unfounded / cancelled): 1.8%2020 · Arrest / citation: 34.6%2020 · Report taken, no arrest: 28.6%2020 · Resolved on scene: 25.1%2020 · Unable to locate: 9.9%2020 · Other (unfounded / cancelled): 1.8%2021 · Arrest / citation: 32.5%2021 · Report taken, no arrest: 27.7%2021 · Resolved on scene: 23.6%2021 · Unable to locate: 14.0%2021 · Other (unfounded / cancelled): 2.2%2022 · Arrest / citation: 22.8%2022 · Report taken, no arrest: 31.2%2022 · Resolved on scene: 24.8%2022 · Unable to locate: 19.3%2022 · Other (unfounded / cancelled): 1.9%2023 · Arrest / citation: 23.6%2023 · Report taken, no arrest: 28.4%2023 · Resolved on scene: 24.9%2023 · Unable to locate: 21.2%2023 · Other (unfounded / cancelled): 2.0%2024 · Arrest / citation: 26.7%2024 · Report taken, no arrest: 25.4%2024 · Resolved on scene: 24.1%2024 · Unable to locate: 22.0%2024 · Other (unfounded / cancelled): 1.8%2025 · Arrest / citation: 35.5%2025 · Report taken, no arrest: 17.9%2025 · Resolved on scene: 24.0%2025 · Unable to locate: 21.0%2025 · Other (unfounded / cancelled): 1.7%2026 · Arrest / citation: 38.0%2026 · Report taken, no arrest: 13.8%2026 · Resolved on scene: 24.5%2026 · Unable to locate: 21.8%2026 · Other (unfounded / cancelled): 1.9%2009n=47,5082011n=68,1092013n=62,7132015n=67,4422017n=70,3282019n=83,1942021n=41,5832023n=39,7292025n=52,0382026n=43,411
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)
200947,50833.6%29.1%26.0%9.0%2.3%
201084,84832.2%28.8%28.7%8.3%2.0%
201168,10929.4%29.4%29.2%9.7%2.3%
201264,12526.6%32.0%28.7%10.3%2.5%
201362,71327.3%30.7%28.1%11.1%2.8%
201461,38527.0%33.1%24.5%13.0%2.3%
201567,44227.2%32.8%24.9%13.0%2.1%
201669,44628.7%32.6%24.8%11.8%2.1%
201770,32830.1%32.4%24.7%10.7%2.1%
201875,94434.2%28.6%23.6%11.4%2.1%
201983,19438.3%26.3%23.5%10.2%1.8%
202044,66334.6%28.6%25.1%9.9%1.8%
202141,58332.5%27.7%23.6%14.0%2.2%
202235,60522.8%31.2%24.8%19.3%1.9%
202339,72923.6%28.4%24.9%21.2%2.0%
202441,01126.7%25.4%24.1%22.0%1.8%
202552,03835.5%17.9%24.0%21.0%1.7%
202643,41138.0%13.8%24.5%21.8%1.9%
22% of Traffic Calls End “Unable to Locate,” Up From 12%Report-taken outcomes moved from 33% of calls in 2016 to 14% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Traffic: 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 42% of traffic 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: 26.9 min2010: 18.4 min2011: 19.8 min2012: 21.2 min2013: 23.5 min2014: 31.1 min2015: 30.7 min2016: 29.0 min2017: 27.5 min2018: 36.7 min2019: 30.9 min2020: 27.9 min2021: 42.8 min2022: 50.9 min2023: 62.8 min2024: 78.4 min2025: 75.8 min2026: 76.1 min2009: 38.0 min2010: 29.2 min2011: 35.0 min2012: 34.8 min2013: 38.4 min2014: 49.2 min2015: 46.9 min2016: 44.4 min2017: 42.8 min2018: 57.2 min2019: 50.2 min2020: 46.2 min2021: 66.4 min2022: 71.8 min2023: 81.2 min2024: 100.1 min2025: 106.6 min2026: 124.5 min2009n=21,9102011n=36,1262013n=38,0242015n=41,6772017n=39,5942019n=40,7442021n=27,3762023n=27,7452025n=33,6572026n=28,604
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
200921,91026.9 min38.0 min
201037,19918.4 min29.2 min
201136,12619.8 min35.0 min
201236,89821.2 min34.8 min
201338,02423.5 min38.4 min
201439,54231.1 min49.2 min
201541,67730.7 min46.9 min
201641,42029.0 min44.4 min
201739,59427.5 min42.8 min
201842,26136.7 min57.2 min
201940,74430.9 min50.2 min
202023,85227.9 min46.2 min
202127,37642.8 min66.4 min
202223,98850.9 min71.8 min
202327,74562.8 min81.2 min
202427,34178.4 min100.1 min
202533,65775.8 min106.6 min
202628,60476.1 min124.5 min
The Average Call Waits 124 Minutes for an Officer to ArriveDespite a 25% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 44 minutes in 2016 to 124 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.

Traffic: 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 42% of traffic 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: 33.4%2009 · 0–5 min: 10.0%2009 · 5–30 min: 33.4%2009 · 30–60 min: 10.9%2009 · 1–4 hr: 11.3%2009 · 4–8 hr: 0.9%2009 · Over 8 hr: 0.1%2010 · No recorded response: 35.2%2010 · 0–5 min: 12.8%2010 · 5–30 min: 34.4%2010 · 30–60 min: 9.2%2010 · 1–4 hr: 8.0%2010 · 4–8 hr: 0.5%2010 · Over 8 hr: 0.0%2011 · No recorded response: 34.1%2011 · 0–5 min: 11.8%2011 · 5–30 min: 34.0%2011 · 30–60 min: 9.7%2011 · 1–4 hr: 9.7%2011 · 4–8 hr: 0.6%2011 · Over 8 hr: 0.0%2012 · No recorded response: 33.5%2012 · 0–5 min: 11.4%2012 · 5–30 min: 33.5%2012 · 30–60 min: 10.4%2012 · 1–4 hr: 10.4%2012 · 4–8 hr: 0.7%2012 · Over 8 hr: 0.1%2013 · No recorded response: 34.6%2013 · 0–5 min: 11.8%2013 · 5–30 min: 32.3%2013 · 30–60 min: 10.0%2013 · 1–4 hr: 10.6%2013 · 4–8 hr: 0.8%2013 · Over 8 hr: 0.1%2014 · No recorded response: 34.8%2014 · 0–5 min: 9.7%2014 · 5–30 min: 29.8%2014 · 30–60 min: 10.1%2014 · 1–4 hr: 13.3%2014 · 4–8 hr: 2.1%2014 · Over 8 hr: 0.2%2015 · No recorded response: 32.5%2015 · 0–5 min: 11.9%2015 · 5–30 min: 30.2%2015 · 30–60 min: 10.0%2015 · 1–4 hr: 13.1%2015 · 4–8 hr: 1.9%2015 · Over 8 hr: 0.3%2016 · No recorded response: 32.2%2016 · 0–5 min: 12.7%2016 · 5–30 min: 31.0%2016 · 30–60 min: 9.8%2016 · 1–4 hr: 12.1%2016 · 4–8 hr: 2.0%2016 · Over 8 hr: 0.2%2017 · No recorded response: 32.8%2017 · 0–5 min: 11.6%2017 · 5–30 min: 31.7%2017 · 30–60 min: 10.0%2017 · 1–4 hr: 12.2%2017 · 4–8 hr: 1.6%2017 · Over 8 hr: 0.1%2018 · No recorded response: 36.8%2018 · 0–5 min: 9.7%2018 · 5–30 min: 27.4%2018 · 30–60 min: 9.2%2018 · 1–4 hr: 13.6%2018 · 4–8 hr: 2.9%2018 · Over 8 hr: 0.4%2019 · No recorded response: 39.8%2019 · 0–5 min: 10.5%2019 · 5–30 min: 25.9%2019 · 30–60 min: 8.9%2019 · 1–4 hr: 12.8%2019 · 4–8 hr: 1.9%2019 · Over 8 hr: 0.2%2020 · No recorded response: 40.6%2020 · 0–5 min: 10.6%2020 · 5–30 min: 26.8%2020 · 30–60 min: 8.5%2020 · 1–4 hr: 11.7%2020 · 4–8 hr: 1.6%2020 · Over 8 hr: 0.1%2021 · No recorded response: 40.5%2021 · 0–5 min: 8.6%2021 · 5–30 min: 25.1%2021 · 30–60 min: 9.0%2021 · 1–4 hr: 12.9%2021 · 4–8 hr: 3.0%2021 · Over 8 hr: 0.9%2022 · No recorded response: 30.1%2022 · 0–5 min: 10.6%2022 · 5–30 min: 29.4%2022 · 30–60 min: 9.9%2022 · 1–4 hr: 15.7%2022 · 4–8 hr: 3.1%2022 · Over 8 hr: 1.1%2023 · No recorded response: 35.1%2023 · 0–5 min: 9.4%2023 · 5–30 min: 25.6%2023 · 30–60 min: 8.9%2023 · 1–4 hr: 15.3%2023 · 4–8 hr: 3.9%2023 · Over 8 hr: 1.8%2024 · No recorded response: 36.4%2024 · 0–5 min: 6.8%2024 · 5–30 min: 22.3%2024 · 30–60 min: 9.3%2024 · 1–4 hr: 17.3%2024 · 4–8 hr: 5.8%2024 · Over 8 hr: 2.2%2025 · No recorded response: 43.4%2025 · 0–5 min: 6.4%2025 · 5–30 min: 19.0%2025 · 30–60 min: 8.3%2025 · 1–4 hr: 15.3%2025 · 4–8 hr: 5.1%2025 · Over 8 hr: 2.5%2026 · No recorded response: 50.0%2026 · 0–5 min: 4.3%2026 · 5–30 min: 16.8%2026 · 30–60 min: 7.5%2026 · 1–4 hr: 12.8%2026 · 4–8 hr: 5.3%2026 · Over 8 hr: 3.3%2009n=21,9102011n=36,1262013n=38,0242015n=41,6772017n=39,5942019n=40,7442021n=27,3762023n=27,7452025n=33,6572026n=28,604
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
200921,91033.4%10.0%33.4%10.9%11.3%0.9%0.1%
201037,19935.2%12.8%34.4%9.2%8.0%0.5%0.0%
201136,12634.1%11.8%34.0%9.7%9.7%0.6%0.0%
201236,89833.5%11.4%33.5%10.4%10.4%0.7%0.1%
201338,02434.6%11.8%32.3%10.0%10.6%0.8%0.1%
201439,54234.8%9.7%29.8%10.1%13.3%2.1%0.2%
201541,67732.5%11.9%30.2%10.0%13.1%1.9%0.3%
201641,42032.2%12.7%31.0%9.8%12.1%2.0%0.2%
201739,59432.8%11.6%31.7%10.0%12.2%1.6%0.1%
201842,26136.8%9.7%27.4%9.2%13.6%2.9%0.4%
201940,74439.8%10.5%25.9%8.9%12.8%1.9%0.2%
202023,85240.6%10.6%26.8%8.5%11.7%1.6%0.1%
202127,37640.5%8.6%25.1%9.0%12.9%3.0%0.9%
202223,98830.1%10.6%29.4%9.9%15.7%3.1%1.1%
202327,74535.1%9.4%25.6%8.9%15.3%3.9%1.8%
202427,34136.4%6.8%22.3%9.3%17.3%5.8%2.2%
202533,65743.4%6.4%19.0%8.3%15.3%5.1%2.5%
202628,60450.0%4.3%16.8%7.5%12.8%5.3%3.3%
The Average Call Waits 76 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 76 minutes in 2026, more than double what it was in 2016. 21% of calls took more than an hour to get a response in 2026, compared with 14% 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.