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

Kidnap

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

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

Swipe sideways to see the full chart →
025502009: 16 kidnap calls logged in CAD2010: 23 kidnap calls logged in CAD2011: 24 kidnap calls logged in CAD2012: 20 kidnap calls logged in CAD2013: 28 kidnap calls logged in CAD2014: 21 kidnap calls logged in CAD2015: 22 kidnap calls logged in CAD2016: 22 kidnap calls logged in CAD2017: 21 kidnap calls logged in CAD2018: 24 kidnap calls logged in CAD2019: 31 kidnap calls logged in CAD2020: 25 kidnap calls logged in CAD2021: 28 kidnap calls logged in CAD2022: 35 kidnap calls logged in CAD2023: 41 kidnap calls logged in CAD2024: 33 kidnap calls logged in CAD2025: 32 kidnap calls logged in CAD2026: 24 kidnap calls logged in CAD2009n=162011n=242013n=282015n=222017n=212019n=312021n=282023n=412025n=322026n=24
kidnap calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodKidnap calls logged in CAD
200916
201023
201124
201220
201328
201421
201522
201622
201721
201824
201931
202025
202128
202235
202341
202433
202532
202624
Kidnap Calls Average About 27 a YearSeattle Police logged 470 kidnap calls between 2009 and 2026, with a high of 41 in 2023.

Kidnap: 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: 31.2%2009 · Report taken, no arrest: 56.2%2009 · Other (unfounded / cancelled): 12.5%2010 · Arrest / citation: 21.7%2010 · Report taken, no arrest: 60.9%2010 · Resolved on scene: 17.4%2011 · Arrest / citation: 12.5%2011 · Report taken, no arrest: 75.0%2011 · Resolved on scene: 8.3%2011 · Unable to locate: 4.2%2012 · Arrest / citation: 35.0%2012 · Report taken, no arrest: 60.0%2012 · Resolved on scene: 5.0%2013 · Arrest / citation: 28.6%2013 · Report taken, no arrest: 64.3%2013 · Resolved on scene: 3.6%2013 · Unable to locate: 3.6%2014 · Arrest / citation: 38.1%2014 · Report taken, no arrest: 52.4%2014 · Resolved on scene: 9.5%2015 · Arrest / citation: 22.7%2015 · Report taken, no arrest: 68.2%2015 · Resolved on scene: 4.5%2015 · Unable to locate: 4.5%2016 · Arrest / citation: 27.3%2016 · Report taken, no arrest: 63.6%2016 · Resolved on scene: 9.1%2017 · Arrest / citation: 14.3%2017 · Report taken, no arrest: 81.0%2017 · Other (unfounded / cancelled): 4.8%2018 · Arrest / citation: 37.5%2018 · Report taken, no arrest: 58.3%2018 · Other (unfounded / cancelled): 4.2%2019 · Arrest / citation: 38.7%2019 · Report taken, no arrest: 51.6%2019 · Resolved on scene: 6.5%2019 · Unable to locate: 3.2%2020 · Arrest / citation: 44.0%2020 · Report taken, no arrest: 52.0%2020 · Unable to locate: 4.0%2021 · Arrest / citation: 17.9%2021 · Report taken, no arrest: 82.1%2022 · Arrest / citation: 34.3%2022 · Report taken, no arrest: 62.9%2022 · Other (unfounded / cancelled): 2.9%2023 · Arrest / citation: 24.4%2023 · Report taken, no arrest: 73.2%2023 · Resolved on scene: 2.4%2024 · Arrest / citation: 39.4%2024 · Report taken, no arrest: 51.5%2024 · Resolved on scene: 6.1%2024 · Unable to locate: 3.0%2025 · Arrest / citation: 43.8%2025 · Report taken, no arrest: 46.9%2025 · Resolved on scene: 6.2%2025 · Unable to locate: 3.1%2026 · Arrest / citation: 29.2%2026 · Report taken, no arrest: 66.7%2026 · Resolved on scene: 4.2%2009n=162011n=242013n=282015n=222017n=212019n=312021n=282023n=412025n=322026n=24
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 arrestOther (unfounded / cancelled)Resolved on sceneUnable to locate
20091631.2%56.2%12.5%——
20102321.7%60.9%—17.4%—
20112412.5%75.0%—8.3%4.2%
20122035.0%60.0%—5.0%—
20132828.6%64.3%—3.6%3.6%
20142138.1%52.4%—9.5%—
20152222.7%68.2%—4.5%4.5%
20162227.3%63.6%—9.1%—
20172114.3%81.0%4.8%——
20182437.5%58.3%4.2%——
20193138.7%51.6%—6.5%3.2%
20202544.0%52.0%——4.0%
20212817.9%82.1%———
20223534.3%62.9%2.9%——
20234124.4%73.2%—2.4%—
20243339.4%51.5%—6.1%3.0%
20253243.8%46.9%—6.2%3.1%
20262429.2%66.7%—4.2%—
1% of Kidnap Calls End “Unable to Locate”Across 2009 to 2026, report-taken outcomes were 63% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Kidnap: 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 17% of kidnap 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 min40 min80 min2009: 21.3 min2010: 11.1 min2011: 12.5 min2012: 22.8 min2013: 12.4 min2014: 8.6 min2015: 21.4 min2016: 5.2 min2017: 44.2 min2018: 16.6 min2019: 19.4 min2020: 13.8 min2021: 8.5 min2022: 23.7 min2023: 18.9 min2024: 58.3 min2025: 31.1 min2026: 14.0 min2009: 27.6 min2010: 15.2 min2011: 22.4 min2012: 38.0 min2013: 37.6 min2014: 16.6 min2015: 28.6 min2016: 10.3 min2017: 55.4 min2018: 24.5 min2019: 30.0 min2020: 19.8 min2021: 21.9 min2022: 33.7 min2023: 26.2 min2024: 69.2 min2025: 43.1 min2026: 18.6 min2009n=132011n=202013n=242015n=162017n=152019n=252021n=252023n=332025n=302026n=18
Average response timeAverage dispatch delay
Small sample: Only a small share of kidnap events are called in. The year with the fewest had only 13, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20091321.3 min27.6 min
20101911.1 min15.2 min
20112012.5 min22.4 min
20121722.8 min38.0 min
20132412.4 min37.6 min
2014178.6 min16.6 min
20151621.4 min28.6 min
2016185.2 min10.3 min
20171544.2 min55.4 min
20182016.6 min24.5 min
20192519.4 min30.0 min
20202013.8 min19.8 min
2021258.5 min21.9 min
20223123.7 min33.7 min
20233318.9 min26.2 min
20242858.3 min69.2 min
20253031.1 min43.1 min
20261814.0 min18.6 min
78% of Called-In Kidnap Calls Get a Response Within 30 Minutes27% were answered in under 5 minutes, across all years on record.
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.

Kidnap: 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 17% of kidnap 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 · 0–5 min: 23.1%2009 · 5–30 min: 53.8%2009 · 30–60 min: 15.4%2009 · 1–4 hr: 7.7%2010 · No recorded response: 5.3%2010 · 0–5 min: 42.1%2010 · 5–30 min: 42.1%2010 · 1–4 hr: 10.5%2011 · 0–5 min: 20.0%2011 · 5–30 min: 65.0%2011 · 1–4 hr: 15.0%2012 · 0–5 min: 41.2%2012 · 5–30 min: 29.4%2012 · 30–60 min: 11.8%2012 · 1–4 hr: 17.6%2013 · 0–5 min: 33.3%2013 · 5–30 min: 54.2%2013 · 1–4 hr: 8.3%2013 · Over 8 hr: 4.2%2014 · 0–5 min: 41.2%2014 · 5–30 min: 35.3%2014 · 30–60 min: 23.5%2015 · 0–5 min: 31.2%2015 · 5–30 min: 50.0%2015 · 30–60 min: 12.5%2015 · 4–8 hr: 6.2%2016 · 0–5 min: 16.7%2016 · 5–30 min: 77.8%2016 · 30–60 min: 5.6%2017 · No recorded response: 6.7%2017 · 0–5 min: 20.0%2017 · 5–30 min: 40.0%2017 · 30–60 min: 6.7%2017 · 1–4 hr: 20.0%2017 · 4–8 hr: 6.7%2018 · 0–5 min: 35.0%2018 · 5–30 min: 50.0%2018 · 1–4 hr: 15.0%2019 · 0–5 min: 24.0%2019 · 5–30 min: 60.0%2019 · 1–4 hr: 12.0%2019 · 4–8 hr: 4.0%2020 · 0–5 min: 35.0%2020 · 5–30 min: 50.0%2020 · 30–60 min: 10.0%2020 · 1–4 hr: 5.0%2021 · No recorded response: 4.0%2021 · 0–5 min: 8.0%2021 · 5–30 min: 76.0%2021 · 30–60 min: 4.0%2021 · 1–4 hr: 8.0%2022 · 0–5 min: 12.9%2022 · 5–30 min: 54.8%2022 · 30–60 min: 16.1%2022 · 1–4 hr: 16.1%2023 · 0–5 min: 21.2%2023 · 5–30 min: 63.6%2023 · 30–60 min: 6.1%2023 · 1–4 hr: 6.1%2023 · 4–8 hr: 3.0%2024 · 0–5 min: 21.4%2024 · 5–30 min: 39.3%2024 · 30–60 min: 14.3%2024 · 1–4 hr: 17.9%2024 · 4–8 hr: 3.6%2024 · Over 8 hr: 3.6%2025 · 0–5 min: 36.7%2025 · 5–30 min: 33.3%2025 · 30–60 min: 6.7%2025 · 1–4 hr: 23.3%2026 · No recorded response: 5.6%2026 · 0–5 min: 33.3%2026 · 5–30 min: 38.9%2026 · 30–60 min: 16.7%2026 · 1–4 hr: 5.6%2009n=132011n=202013n=242015n=162017n=152019n=252021n=252023n=332025n=302026n=18
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of kidnap events are called in. The year with the fewest had only 13, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in events0–5 min5–30 min30–60 min1–4 hrNo recorded responseOver 8 hr4–8 hr
20091323.1%53.8%15.4%7.7%———
20101942.1%42.1%—10.5%5.3%——
20112020.0%65.0%—15.0%———
20121741.2%29.4%11.8%17.6%———
20132433.3%54.2%—8.3%—4.2%—
20141741.2%35.3%23.5%————
20151631.2%50.0%12.5%———6.2%
20161816.7%77.8%5.6%————
20171520.0%40.0%6.7%20.0%6.7%—6.7%
20182035.0%50.0%—15.0%———
20192524.0%60.0%—12.0%——4.0%
20202035.0%50.0%10.0%5.0%———
2021258.0%76.0%4.0%8.0%4.0%——
20223112.9%54.8%16.1%16.1%———
20233321.2%63.6%6.1%6.1%——3.0%
20242821.4%39.3%14.3%17.9%—3.6%3.6%
20253036.7%33.3%6.7%23.3%———
20261833.3%38.9%16.7%5.6%5.6%——
13% of Called-In Kidnap Calls Wait Over an Hour for a ResponseAcross 2009 to 2026, 13% of called-in events took more than an hour to get a response.
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.