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

Rape

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

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

Swipe sideways to see the full chart →
05001,0002009: 308 rape calls logged in CAD2010: 524 rape calls logged in CAD2011: 545 rape calls logged in CAD2012: 542 rape calls logged in CAD2013: 585 rape calls logged in CAD2014: 487 rape calls logged in CAD2015: 561 rape calls logged in CAD2016: 695 rape calls logged in CAD2017: 706 rape calls logged in CAD2018: 876 rape calls logged in CAD2019: 788 rape calls logged in CAD2020: 679 rape calls logged in CAD2021: 733 rape calls logged in CAD2022: 766 rape calls logged in CAD2023: 815 rape calls logged in CAD2024: 877 rape calls logged in CAD2025: 854 rape calls logged in CAD2026: 725 rape calls logged in CAD2009n=3082011n=5452013n=5852015n=5612017n=7062019n=7882021n=7332023n=8152025n=8542026n=725
rape calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodRape calls logged in CAD
2009308
2010524
2011545
2012542
2013585
2014487
2015561
2016695
2017706
2018876
2019788
2020679
2021733
2022766
2023815
2024877
2025854
2026725
Rape Calls Are Holding Near Their PeakSeattle Police logged 854 rape calls in 2025, the most recent full year, close to the 877 in 2024.

Rape: 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: 8.8%2009 · Report taken, no arrest: 79.5%2009 · Resolved on scene: 4.5%2009 · Unable to locate: 4.9%2009 · Other (unfounded / cancelled): 2.2%2010 · Arrest / citation: 7.6%2010 · Report taken, no arrest: 79.2%2010 · Resolved on scene: 7.1%2010 · Unable to locate: 4.0%2010 · Other (unfounded / cancelled): 2.1%2011 · Arrest / citation: 5.9%2011 · Report taken, no arrest: 80.4%2011 · Resolved on scene: 9.9%2011 · Unable to locate: 2.6%2011 · Other (unfounded / cancelled): 1.3%2012 · Arrest / citation: 7.6%2012 · Report taken, no arrest: 81.4%2012 · Resolved on scene: 6.3%2012 · Unable to locate: 2.8%2012 · Other (unfounded / cancelled): 2.1%2013 · Arrest / citation: 6.2%2013 · Report taken, no arrest: 84.3%2013 · Resolved on scene: 5.5%2013 · Unable to locate: 2.9%2013 · Other (unfounded / cancelled): 1.2%2014 · Arrest / citation: 5.7%2014 · Report taken, no arrest: 87.5%2014 · Resolved on scene: 3.1%2014 · Unable to locate: 2.9%2014 · Other (unfounded / cancelled): 0.8%2015 · Arrest / citation: 6.1%2015 · Report taken, no arrest: 84.3%2015 · Resolved on scene: 5.7%2015 · Unable to locate: 3.4%2015 · Other (unfounded / cancelled): 0.5%2016 · Arrest / citation: 5.8%2016 · Report taken, no arrest: 84.7%2016 · Resolved on scene: 4.6%2016 · Unable to locate: 3.5%2016 · Other (unfounded / cancelled): 1.5%2017 · Arrest / citation: 4.2%2017 · Report taken, no arrest: 86.7%2017 · Resolved on scene: 5.2%2017 · Unable to locate: 2.3%2017 · Other (unfounded / cancelled): 1.5%2018 · Arrest / citation: 4.7%2018 · Report taken, no arrest: 86.1%2018 · Resolved on scene: 4.6%2018 · Unable to locate: 3.2%2018 · Other (unfounded / cancelled): 1.5%2019 · Arrest / citation: 6.6%2019 · Report taken, no arrest: 84.5%2019 · Resolved on scene: 4.8%2019 · Unable to locate: 3.2%2019 · Other (unfounded / cancelled): 0.9%2020 · Arrest / citation: 5.4%2020 · Report taken, no arrest: 84.2%2020 · Resolved on scene: 5.0%2020 · Unable to locate: 4.0%2020 · Other (unfounded / cancelled): 1.3%2021 · Arrest / citation: 4.8%2021 · Report taken, no arrest: 83.1%2021 · Resolved on scene: 5.2%2021 · Unable to locate: 5.3%2021 · Other (unfounded / cancelled): 1.6%2022 · Arrest / citation: 5.9%2022 · Report taken, no arrest: 86.0%2022 · Resolved on scene: 3.4%2022 · Unable to locate: 4.4%2022 · Other (unfounded / cancelled): 0.2%2023 · Arrest / citation: 4.3%2023 · Report taken, no arrest: 83.1%2023 · Resolved on scene: 4.0%2023 · Unable to locate: 7.7%2023 · Other (unfounded / cancelled): 0.8%2024 · Arrest / citation: 3.5%2024 · Report taken, no arrest: 79.7%2024 · Resolved on scene: 5.2%2024 · Unable to locate: 10.5%2024 · Other (unfounded / cancelled): 1.0%2025 · Arrest / citation: 6.3%2025 · Report taken, no arrest: 79.2%2025 · Resolved on scene: 3.9%2025 · Unable to locate: 8.8%2025 · Other (unfounded / cancelled): 1.9%2026 · Arrest / citation: 5.4%2026 · Report taken, no arrest: 80.0%2026 · Resolved on scene: 4.8%2026 · Unable to locate: 8.1%2026 · Other (unfounded / cancelled): 1.6%2009n=3082011n=5452013n=5852015n=5612017n=7062019n=7882021n=7332023n=8152025n=8542026n=725
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)
20093088.8%79.5%4.5%4.9%2.2%
20105247.6%79.2%7.1%4.0%2.1%
20115455.9%80.4%9.9%2.6%1.3%
20125427.6%81.4%6.3%2.8%2.1%
20135856.2%84.3%5.5%2.9%1.2%
20144875.7%87.5%3.1%2.9%0.8%
20155616.1%84.3%5.7%3.4%0.5%
20166955.8%84.7%4.6%3.5%1.5%
20177064.2%86.7%5.2%2.3%1.5%
20188764.7%86.1%4.6%3.2%1.5%
20197886.6%84.5%4.8%3.2%0.9%
20206795.4%84.2%5.0%4.0%1.3%
20217334.8%83.1%5.2%5.3%1.6%
20227665.9%86.0%3.4%4.4%0.2%
20238154.3%83.1%4.0%7.7%0.8%
20248773.5%79.7%5.2%10.5%1.0%
20258546.3%79.2%3.9%8.8%1.9%
20267255.4%80.0%4.8%8.1%1.6%
8% of Rape Calls End “Unable to Locate,” Up From 4%Report-taken outcomes moved from 85% of calls in 2016 to 80% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Rape: 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 30% of rape 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: 23.9 min2010: 24.0 min2011: 23.1 min2012: 33.8 min2013: 31.9 min2014: 41.0 min2015: 41.6 min2016: 33.2 min2017: 42.6 min2018: 50.2 min2019: 54.0 min2020: 54.8 min2021: 77.1 min2022: 77.9 min2023: 99.6 min2024: 151.0 min2025: 159.1 min2026: 145.5 min2009: 35.9 min2010: 34.7 min2011: 35.5 min2012: 46.9 min2013: 63.0 min2014: 54.9 min2015: 54.3 min2016: 48.7 min2017: 55.7 min2018: 65.0 min2019: 67.6 min2020: 68.0 min2021: 93.5 min2022: 97.7 min2023: 114.4 min2024: 177.4 min2025: 178.8 min2026: 159.2 min2009n=2132011n=3802013n=4492015n=4082017n=4862019n=5482021n=5472023n=5352025n=5582026n=469
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
200921323.9 min35.9 min
201039124.0 min34.7 min
201138023.1 min35.5 min
201240433.8 min46.9 min
201344931.9 min63.0 min
201438641.0 min54.9 min
201540841.6 min54.3 min
201650033.2 min48.7 min
201748642.6 min55.7 min
201861850.2 min65.0 min
201954854.0 min67.6 min
202047954.8 min68.0 min
202154777.1 min93.5 min
202251577.9 min97.7 min
202353599.6 min114.4 min
2024599151.0 min177.4 min
2025558159.1 min178.8 min
2026469145.5 min159.2 min
The Average Call Waits 159 Minutes for an Officer to ArriveAs calls rose 23% between 2016 and 2025, average response time has grown about 3-fold in the past 10 years, from 49 minutes in 2016 to 159 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.

Rape: 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 30% of rape 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: 2.4%2009 · 0–5 min: 14.1%2009 · 5–30 min: 50.7%2009 · 30–60 min: 16.4%2009 · 1–4 hr: 15.0%2009 · 4–8 hr: 1.4%2010 · No recorded response: 2.3%2010 · 0–5 min: 18.9%2010 · 5–30 min: 44.2%2010 · 30–60 min: 17.9%2010 · 1–4 hr: 15.6%2010 · 4–8 hr: 1.0%2011 · No recorded response: 2.9%2011 · 0–5 min: 20.0%2011 · 5–30 min: 43.7%2011 · 30–60 min: 14.7%2011 · 1–4 hr: 17.9%2011 · 4–8 hr: 0.8%2012 · No recorded response: 2.7%2012 · 0–5 min: 14.8%2012 · 5–30 min: 42.1%2012 · 30–60 min: 17.6%2012 · 1–4 hr: 20.1%2012 · 4–8 hr: 2.7%2013 · No recorded response: 2.7%2013 · 0–5 min: 14.7%2013 · 5–30 min: 42.3%2013 · 30–60 min: 18.3%2013 · 1–4 hr: 19.8%2013 · 4–8 hr: 1.8%2013 · Over 8 hr: 0.5%2014 · No recorded response: 3.4%2014 · 0–5 min: 14.5%2014 · 5–30 min: 41.7%2014 · 30–60 min: 12.7%2014 · 1–4 hr: 23.3%2014 · 4–8 hr: 4.4%2015 · No recorded response: 4.9%2015 · 0–5 min: 12.5%2015 · 5–30 min: 37.0%2015 · 30–60 min: 17.6%2015 · 1–4 hr: 24.5%2015 · 4–8 hr: 3.2%2015 · Over 8 hr: 0.2%2016 · No recorded response: 2.8%2016 · 0–5 min: 14.0%2016 · 5–30 min: 45.2%2016 · 30–60 min: 15.6%2016 · 1–4 hr: 19.8%2016 · 4–8 hr: 2.0%2016 · Over 8 hr: 0.6%2017 · No recorded response: 3.9%2017 · 0–5 min: 9.7%2017 · 5–30 min: 40.3%2017 · 30–60 min: 18.3%2017 · 1–4 hr: 25.3%2017 · 4–8 hr: 2.5%2018 · No recorded response: 5.0%2018 · 0–5 min: 7.4%2018 · 5–30 min: 37.2%2018 · 30–60 min: 16.0%2018 · 1–4 hr: 30.4%2018 · 4–8 hr: 3.6%2018 · Over 8 hr: 0.3%2019 · No recorded response: 3.8%2019 · 0–5 min: 13.1%2019 · 5–30 min: 33.0%2019 · 30–60 min: 15.2%2019 · 1–4 hr: 29.7%2019 · 4–8 hr: 4.6%2019 · Over 8 hr: 0.6%2020 · No recorded response: 6.3%2020 · 0–5 min: 7.9%2020 · 5–30 min: 37.6%2020 · 30–60 min: 15.0%2020 · 1–4 hr: 27.1%2020 · 4–8 hr: 6.0%2021 · No recorded response: 5.7%2021 · 0–5 min: 9.0%2021 · 5–30 min: 30.9%2021 · 30–60 min: 13.7%2021 · 1–4 hr: 32.4%2021 · 4–8 hr: 6.0%2021 · Over 8 hr: 2.4%2022 · No recorded response: 5.6%2022 · 0–5 min: 8.7%2022 · 5–30 min: 32.8%2022 · 30–60 min: 13.0%2022 · 1–4 hr: 28.7%2022 · 4–8 hr: 8.3%2022 · Over 8 hr: 2.7%2023 · No recorded response: 8.4%2023 · 0–5 min: 8.0%2023 · 5–30 min: 28.8%2023 · 30–60 min: 11.8%2023 · 1–4 hr: 30.5%2023 · 4–8 hr: 8.2%2023 · Over 8 hr: 4.3%2024 · No recorded response: 8.2%2024 · 0–5 min: 5.8%2024 · 5–30 min: 21.9%2024 · 30–60 min: 13.0%2024 · 1–4 hr: 29.7%2024 · 4–8 hr: 13.0%2024 · Over 8 hr: 8.3%2025 · No recorded response: 10.8%2025 · 0–5 min: 5.6%2025 · 5–30 min: 22.6%2025 · 30–60 min: 12.4%2025 · 1–4 hr: 28.7%2025 · 4–8 hr: 12.0%2025 · Over 8 hr: 8.1%2026 · No recorded response: 11.9%2026 · 0–5 min: 6.8%2026 · 5–30 min: 25.2%2026 · 30–60 min: 11.3%2026 · 1–4 hr: 26.2%2026 · 4–8 hr: 9.8%2026 · Over 8 hr: 8.7%2009n=2132011n=3802013n=4492015n=4082017n=4862019n=5482021n=5472023n=5352025n=5582026n=469
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
20092132.4%14.1%50.7%16.4%15.0%1.4%—
20103912.3%18.9%44.2%17.9%15.6%1.0%—
20113802.9%20.0%43.7%14.7%17.9%0.8%—
20124042.7%14.8%42.1%17.6%20.1%2.7%—
20134492.7%14.7%42.3%18.3%19.8%1.8%0.5%
20143863.4%14.5%41.7%12.7%23.3%4.4%—
20154084.9%12.5%37.0%17.6%24.5%3.2%0.2%
20165002.8%14.0%45.2%15.6%19.8%2.0%0.6%
20174863.9%9.7%40.3%18.3%25.3%2.5%—
20186185.0%7.4%37.2%16.0%30.4%3.6%0.3%
20195483.8%13.1%33.0%15.2%29.7%4.6%0.6%
20204796.3%7.9%37.6%15.0%27.1%6.0%—
20215475.7%9.0%30.9%13.7%32.4%6.0%2.4%
20225155.6%8.7%32.8%13.0%28.7%8.3%2.7%
20235358.4%8.0%28.8%11.8%30.5%8.2%4.3%
20245998.2%5.8%21.9%13.0%29.7%13.0%8.3%
202555810.8%5.6%22.6%12.4%28.7%12.0%8.1%
202646911.9%6.8%25.2%11.3%26.2%9.8%8.7%
The Average Call Waits 146 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 146 minutes in 2026, more than double what it was in 2016. 45% 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.