Disclaimer: This site uses publicly accessible data from the City of Seattle. We use artificial intelligence to interpret and visualize the data. We present the data as is. Any further analysis or interpretation of the data is strictly the responsibility of the end user.
Cookies: This site uses cookies and similar browser storage, including Google Analytics, to measure traffic and to remember your choice. You must accept cookies to view this site. See our Privacy Policy.
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 →
Swipe sideways to see the full chart →
kidnap calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Kidnap calls logged in CAD
2009
16
2010
23
2011
24
2012
20
2013
28
2014
21
2015
22
2016
22
2017
21
2018
24
2019
31
2020
25
2021
28
2022
35
2023
41
2024
33
2025
32
2026
24
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 →
Swipe sideways to see the full chart →
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
Period
Events
Arrest / citation
Report taken, no arrest
Other (unfounded / cancelled)
Resolved on scene
Unable to locate
2009
16
31.2%
56.2%
12.5%
—
—
2010
23
21.7%
60.9%
—
17.4%
—
2011
24
12.5%
75.0%
—
8.3%
4.2%
2012
20
35.0%
60.0%
—
5.0%
—
2013
28
28.6%
64.3%
—
3.6%
3.6%
2014
21
38.1%
52.4%
—
9.5%
—
2015
22
22.7%
68.2%
—
4.5%
4.5%
2016
22
27.3%
63.6%
—
9.1%
—
2017
21
14.3%
81.0%
4.8%
—
—
2018
24
37.5%
58.3%
4.2%
—
—
2019
31
38.7%
51.6%
—
6.5%
3.2%
2020
25
44.0%
52.0%
—
—
4.0%
2021
28
17.9%
82.1%
—
—
—
2022
35
34.3%
62.9%
2.9%
—
—
2023
41
24.4%
73.2%
—
2.4%
—
2024
33
39.4%
51.5%
—
6.1%
3.0%
2025
32
43.8%
46.9%
—
6.2%
3.1%
2026
24
29.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 →
Swipe sideways to see the full chart →
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
Period
Called-in events
Average dispatch delay
Average response time
2009
13
21.3 min
27.6 min
2010
19
11.1 min
15.2 min
2011
20
12.5 min
22.4 min
2012
17
22.8 min
38.0 min
2013
24
12.4 min
37.6 min
2014
17
8.6 min
16.6 min
2015
16
21.4 min
28.6 min
2016
18
5.2 min
10.3 min
2017
15
44.2 min
55.4 min
2018
20
16.6 min
24.5 min
2019
25
19.4 min
30.0 min
2020
20
13.8 min
19.8 min
2021
25
8.5 min
21.9 min
2022
31
23.7 min
33.7 min
2023
33
18.9 min
26.2 min
2024
28
58.3 min
69.2 min
2025
30
31.1 min
43.1 min
2026
18
14.0 min
18.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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of kidnap calls. The year with the fewest had only 5, 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
Period
Called-in events
Average dispatch delay
Average response time
2009
5
4.0 min
8.8 min
2010
7
0.9 min
3.2 min
2011
8
3.9 min
8.4 min
2012
10
1.1 min
4.6 min
2013
11
1.0 min
6.4 min
2014
9
1.9 min
6.6 min
2015
11
3.5 min
11.5 min
2016
9
1.5 min
5.8 min
2017
6
2.2 min
7.8 min
2018
15
3.6 min
12.6 min
2019
11
1.4 min
6.0 min
2020
13
2.3 min
9.7 min
2021
11
1.2 min
12.6 min
2022
15
4.5 min
10.0 min
2023
23
3.7 min
10.6 min
2024
11
1.9 min
7.7 min
2025
17
1.7 min
6.1 min
2026
12
4.0 min
10.1 min
Priority 1 Calls Waited 10 Minutes on Average in 2026That is the average across 12 called-in Priority 1 events in 2026. Counts this small can swing a lot from year to year.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of kidnap calls. The year with the fewest had only 1, 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
Period
Called-in events
Average dispatch delay
Average response time
2009
2
2.8 min
6.6 min
2010
6
2.9 min
9.9 min
2011
4
8.2 min
15.6 min
2012
4
38.4 min
50.5 min
2013
6
24.4 min
32.2 min
2014
6
5.4 min
19.9 min
2015
1
0.5 min
3.6 min
2016
4
0.9 min
10.3 min
2017
6
19.4 min
25.0 min
2018
2
72.0 min
75.9 min
2019
10
16.4 min
34.2 min
2020
4
2.0 min
6.3 min
2021
8
14.9 min
35.7 min
2022
10
34.5 min
48.9 min
2023
4
87.7 min
95.3 min
2024
8
27.5 min
41.7 min
2025
6
72.6 min
91.1 min
2026
4
24.8 min
29.8 min
Priority 2 Calls Waited 30 Minutes on Average in 2026That is the average across 4 called-in Priority 2 events in 2026. Counts this small can swing a lot from year to year.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of kidnap calls. The year with the fewest had only 2, 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
Period
Called-in events
Average dispatch delay
Average response time
2009
6
41.9 min
50.4 min
2010
6
31.3 min
38.3 min
2011
8
23.3 min
39.8 min
2012
2
13.5 min
100.4 min
2013
7
20.0 min
91.3 min
2014
2
48.4 min
52.1 min
2015
4
75.9 min
81.7 min
2016
4
19.0 min
22.9 min
2017
3
177.7 min
201.1 min
2018
3
44.9 min
49.7 min
2019
3
77.6 min
89.4 min
2020
2
25.2 min
29.0 min
2021
6
13.3 min
20.6 min
2022
5
32.9 min
49.2 min
2023
4
43.1 min
56.6 min
2024
8
174.0 min
190.0 min
2025
6
59.2 min
88.5 min
2026
2
52.7 min
52.7 min
Priority 3 Calls Waited 53 Minutes on Average in 2026That is the average across 2 called-in Priority 3 events in 2026. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
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
Period
Called-in events
0–5 min
5–30 min
30–60 min
1–4 hr
No recorded response
Over 8 hr
4–8 hr
2009
13
23.1%
53.8%
15.4%
7.7%
—
—
—
2010
19
42.1%
42.1%
—
10.5%
5.3%
—
—
2011
20
20.0%
65.0%
—
15.0%
—
—
—
2012
17
41.2%
29.4%
11.8%
17.6%
—
—
—
2013
24
33.3%
54.2%
—
8.3%
—
4.2%
—
2014
17
41.2%
35.3%
23.5%
—
—
—
—
2015
16
31.2%
50.0%
12.5%
—
—
—
6.2%
2016
18
16.7%
77.8%
5.6%
—
—
—
—
2017
15
20.0%
40.0%
6.7%
20.0%
6.7%
—
6.7%
2018
20
35.0%
50.0%
—
15.0%
—
—
—
2019
25
24.0%
60.0%
—
12.0%
—
—
4.0%
2020
20
35.0%
50.0%
10.0%
5.0%
—
—
—
2021
25
8.0%
76.0%
4.0%
8.0%
4.0%
—
—
2022
31
12.9%
54.8%
16.1%
16.1%
—
—
—
2023
33
21.2%
63.6%
6.1%
6.1%
—
—
3.0%
2024
28
21.4%
39.3%
14.3%
17.9%
—
3.6%
3.6%
2025
30
36.7%
33.3%
6.7%
23.3%
—
—
—
2026
18
33.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.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of kidnap calls. The year with the fewest had only 5, 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
Period
Called-in events
0–5 min
5–30 min
30–60 min
1–4 hr
2009
5
40.0%
60.0%
—
—
2010
7
85.7%
14.3%
—
—
2011
8
37.5%
62.5%
—
—
2012
10
60.0%
40.0%
—
—
2013
11
45.5%
54.5%
—
—
2014
9
44.4%
55.5%
—
—
2015
11
36.4%
54.5%
9.1%
—
2016
9
22.2%
77.8%
—
—
2017
6
33.3%
66.7%
—
—
2018
15
33.3%
60.0%
—
6.7%
2019
11
54.5%
45.5%
—
—
2020
13
30.8%
61.5%
7.7%
—
2021
11
18.2%
72.7%
9.1%
—
2022
15
20.0%
73.3%
6.7%
—
2023
23
30.4%
60.9%
4.3%
4.3%
2024
11
36.4%
63.6%
—
—
2025
17
64.7%
35.3%
—
—
2026
12
41.7%
50.0%
8.3%
—
0% of Priority 1 Calls Took Over an Hour in 2026That is 0% of 12 called-in Priority 1 events. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of kidnap calls. The year with the fewest had only 1, 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
Period
Called-in events
0–5 min
5–30 min
30–60 min
1–4 hr
No recorded response
4–8 hr
2009
2
50.0%
50.0%
—
—
—
—
2010
6
33.3%
66.7%
—
—
—
—
2011
4
25.0%
75.0%
—
—
—
—
2012
4
25.0%
25.0%
25.0%
25.0%
—
—
2013
6
33.3%
50.0%
—
16.7%
—
—
2014
6
50.0%
16.7%
33.3%
—
—
—
2015
1
100.0%
—
—
—
—
—
2016
4
—
100.0%
—
—
—
—
2017
6
16.7%
33.3%
16.7%
16.7%
16.7%
—
2018
2
50.0%
—
—
50.0%
—
—
2019
10
—
80.0%
—
20.0%
—
—
2020
4
50.0%
50.0%
—
—
—
—
2021
8
—
75.0%
—
25.0%
—
—
2022
10
—
40.0%
30.0%
30.0%
—
—
2023
4
—
75.0%
—
—
—
25.0%
2024
8
—
50.0%
25.0%
25.0%
—
—
2025
6
—
50.0%
—
50.0%
—
—
2026
4
—
25.0%
50.0%
—
25.0%
—
0% of Priority 2 Calls Took Over an Hour in 2026That is 0% of 4 called-in Priority 2 events. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of kidnap calls. The year with the fewest had only 2, 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
Period
Called-in events
5–30 min
30–60 min
1–4 hr
No recorded response
0–5 min
Over 8 hr
4–8 hr
2009
6
50.0%
33.3%
16.7%
—
—
—
—
2010
6
50.0%
—
33.3%
16.7%
—
—
—
2011
8
62.5%
—
37.5%
—
—
—
—
2012
2
—
50.0%
50.0%
—
—
—
—
2013
7
57.1%
—
14.3%
—
14.3%
14.3%
—
2014
2
—
100.0%
—
—
—
—
—
2015
4
50.0%
25.0%
—
—
—
—
25.0%
2016
4
75.0%
25.0%
—
—
—
—
—
2017
3
—
—
66.7%
—
—
—
33.3%
2018
3
33.3%
—
33.3%
—
33.3%
—
—
2019
3
66.7%
—
—
—
—
—
33.3%
2020
2
—
50.0%
—
—
50.0%
—
—
2021
6
83.3%
—
—
16.7%
—
—
—
2022
5
40.0%
20.0%
20.0%
—
20.0%
—
—
2023
4
50.0%
25.0%
25.0%
—
—
—
—
2024
8
—
25.0%
37.5%
—
12.5%
12.5%
12.5%
2025
6
16.7%
33.3%
50.0%
—
—
—
—
2026
2
—
—
50.0%
—
50.0%
—
—
50% of Priority 3 Calls Took Over an Hour in 2026That is 50% of 2 called-in Priority 3 events. Counts this small can swing a lot from year to year.
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.
Showing the 12 full calendar months, Sep 2025 through Aug 2026, one bar per month. The current month is left out because it is incomplete.
Small sample: this category had 31 events in this period. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each month shows its count.
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 →
Swipe sideways to see the full chart →
kidnap calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Kidnap calls logged in CAD
Sep 2025
3
Oct 2025
2
Nov 2025
1
Dec 2025
1
Jan 2026
4
Feb 2026
3
Mar 2026
2
Apr 2026
4
May 2026
3
Jun 2026
4
Jul 2026
2
Aug 2026
2
Kidnap Calls Totaled 31 Over the Last 12 MonthsSeattle Police logged 4 kidnap calls in the busiest month (Jan 2026) and 1 in the quietest (Nov 2025). Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
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
Period
Events
Arrest / citation
Report taken, no arrest
Resolved on scene
Sep 2025
3
100.0%
—
—
Oct 2025
2
—
100.0%
—
Nov 2025
1
100.0%
—
—
Dec 2025
1
—
100.0%
—
Jan 2026
4
50.0%
50.0%
—
Feb 2026
3
33.3%
33.3%
33.3%
Mar 2026
2
—
100.0%
—
Apr 2026
4
25.0%
75.0%
—
May 2026
3
—
100.0%
—
Jun 2026
4
25.0%
75.0%
—
Jul 2026
2
50.0%
50.0%
—
Aug 2026
2
50.0%
50.0%
—
“Unable to Locate” Ended 0% of Kidnap Calls Over the Last 12 MonthsReport-taken outcomes were 61% of calls over the period.
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of kidnap events are called in. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
3
36.8 min
89.4 min
Oct 2025
2
1.9 min
4.1 min
Nov 2025
1
0.2 min
3.7 min
Dec 2025
1
10.5 min
16.4 min
Jan 2026
3
11.2 min
15.2 min
Feb 2026
1
2.9 min
5.7 min
Mar 2026
2
26.2 min
2.6 min
Apr 2026
2
3.4 min
24.2 min
May 2026
3
2.7 min
5.8 min
Jun 2026
4
1.6 min
10.9 min
Jul 2026
2
18.9 min
24.0 min
Aug 2026
1
104.8 min
104.8 min
Called-In Events Averaged 25 Minutes to Get an Officer Over the Last 12 MonthsBased on 25 called-in events with a recorded arrival. Counts this small can swing from one month to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of kidnap calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
1
1.1 min
3.6 min
Oct 2025
1
1.8 min
1.8 min
Nov 2025
1
0.2 min
3.7 min
Dec 2025
1
10.5 min
16.4 min
Jan 2026
2
16.5 min
22.6 min
Feb 2026
1
2.9 min
5.7 min
Mar 2026
1
0.5 min
2.6 min
Apr 2026
1
1.5 min
9.3 min
May 2026
2
1.5 min
4.3 min
Jun 2026
4
1.6 min
10.9 min
Jul 2026
1
0.9 min
6.5 min
Aug 2026
0
—
—
94% of Called-In Priority 1 Calls Got a Response Within 30 Minutes50% were answered in under 5 minutes over the last 12 months.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of kidnap calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
0
—
—
Oct 2025
1
2.0 min
6.4 min
Nov 2025
0
—
—
Dec 2025
0
—
—
Jan 2026
0
—
—
Feb 2026
0
—
—
Mar 2026
1
52.0 min
—
Apr 2026
1
5.3 min
39.1 min
May 2026
1
5.2 min
8.8 min
Jun 2026
0
—
—
Jul 2026
1
37.0 min
41.6 min
Aug 2026
0
—
—
Priority 2 Calls Averaged 24 Minutes to Get an Officer Over the Last 12 MonthsBased on 4 called-in Priority 2 events with a recorded arrival. Counts this small can swing from one month to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of kidnap calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
2
54.6 min
132.3 min
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
0
—
—
Jan 2026
1
0.6 min
0.6 min
Feb 2026
0
—
—
Mar 2026
0
—
—
Apr 2026
0
—
—
May 2026
0
—
—
Jun 2026
0
—
—
Jul 2026
0
—
—
Aug 2026
1
104.8 min
104.8 min
Priority 3 Calls Averaged 93 Minutes to Get an Officer Over the Last 12 MonthsBased on 4 called-in Priority 3 events with a recorded arrival. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
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 month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
0–5 min
1–4 hr
5–30 min
30–60 min
No recorded response
Sep 2025
3
33.3%
66.7%
—
—
—
Oct 2025
2
50.0%
—
50.0%
—
—
Nov 2025
1
100.0%
—
—
—
—
Dec 2025
1
—
—
100.0%
—
—
Jan 2026
3
66.7%
—
—
33.3%
—
Feb 2026
1
—
—
100.0%
—
—
Mar 2026
2
50.0%
—
—
—
50.0%
Apr 2026
2
—
—
50.0%
50.0%
—
May 2026
3
66.7%
—
33.3%
—
—
Jun 2026
4
25.0%
—
75.0%
—
—
Jul 2026
2
—
—
50.0%
50.0%
—
Aug 2026
1
—
100.0%
—
—
—
12% of Called-In Events Took Over an Hour Over the Last 12 MonthsThat is 12% of 25 called-in events. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of kidnap calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
0–5 min
5–30 min
30–60 min
Sep 2025
1
100.0%
—
—
Oct 2025
1
100.0%
—
—
Nov 2025
1
100.0%
—
—
Dec 2025
1
—
100.0%
—
Jan 2026
2
50.0%
—
50.0%
Feb 2026
1
—
100.0%
—
Mar 2026
1
100.0%
—
—
Apr 2026
1
—
100.0%
—
May 2026
2
100.0%
—
—
Jun 2026
4
25.0%
75.0%
—
Jul 2026
1
—
100.0%
—
Aug 2026
0
—
—
—
No Called-In Priority 1 Calls Took Over an Hour to Get a ResponseNone of the 16 called-in events over the last 12 months took more than an hour.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of kidnap calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
No recorded response
30–60 min
Sep 2025
0
—
—
—
Oct 2025
1
100.0%
—
—
Nov 2025
0
—
—
—
Dec 2025
0
—
—
—
Jan 2026
0
—
—
—
Feb 2026
0
—
—
—
Mar 2026
1
—
100.0%
—
Apr 2026
1
—
—
100.0%
May 2026
1
100.0%
—
—
Jun 2026
0
—
—
—
Jul 2026
1
—
—
100.0%
Aug 2026
0
—
—
—
0% of Priority 2 Calls Took Over an Hour Over the Last 12 MonthsThat is 0% of 5 called-in Priority 2 events. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of kidnap calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
1–4 hr
0–5 min
Sep 2025
2
100.0%
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
0
—
—
Jan 2026
1
—
100.0%
Feb 2026
0
—
—
Mar 2026
0
—
—
Apr 2026
0
—
—
May 2026
0
—
—
Jun 2026
0
—
—
Jul 2026
0
—
—
Aug 2026
1
100.0%
—
75% of Priority 3 Calls Took Over an Hour Over the Last 12 MonthsThat is 75% of 4 called-in Priority 3 events. Counts this small can swing from one month to the next.
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.
Showing the 12 most recent full weeks (Monday to Sunday): Jun 15 through Sep 6, 2026, one bar per week, labeled by its first day. The current week is left out because it is incomplete.
Small sample: this category had 8 events in this period, with no dispatches in 7 of the 12 weeks. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each week shows its count.
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 →
Swipe sideways to see the full chart →
kidnap calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Kidnap calls logged in CAD
Week of Jun 15
3
Week of Jun 22
1
Week of Jun 29
—
Week of Jul 6
2
Week of Jul 13
—
Week of Jul 20
—
Week of Jul 27
—
Week of Aug 3
1
Week of Aug 10
1
Week of Aug 17
—
Week of Aug 24
—
Week of Aug 31
—
Kidnap Calls Totaled 8 Over the Last 12 WeeksSeattle Police logged 3 kidnap calls in the busiest week (Week of Jun 15); 7 of the 12 weeks had none. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
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
Period
Events
Arrest / citation
Report taken, no arrest
Week of Jun 15
0
33.3%
66.7%
Week of Jun 22
0
—
100.0%
Week of Jul 6
0
50.0%
50.0%
Week of Aug 3
0
100.0%
—
Week of Aug 10
0
—
100.0%
“Unable to Locate” Ended 0% of Kidnap Calls Over the Last 12 WeeksReport-taken outcomes were 63% of calls over the period.
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of kidnap events are called in. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
3
1.9 min
13.7 min
Week of Jun 22
1
0.4 min
2.2 min
Week of Jun 29
0
—
—
Week of Jul 6
2
18.9 min
24.0 min
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
104.8 min
104.8 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Called-In Events Averaged 28 Minutes to Get an Officer Over the Last 12 WeeksBased on 7 called-in events with a recorded arrival. Counts this small can swing from one week to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of kidnap calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
3
1.9 min
13.7 min
Week of Jun 22
1
0.4 min
2.2 min
Week of Jun 29
0
—
—
Week of Jul 6
1
0.9 min
6.5 min
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 1 Calls Averaged 10.0 Minutes to Get an Officer Over the Last 12 WeeksBased on 5 called-in Priority 1 events with a recorded arrival. Counts this small can swing from one week to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of kidnap calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
0
—
—
Week of Jul 6
1
37.0 min
41.6 min
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 2 Calls Averaged 42 Minutes to Get an Officer Over the Last 12 WeeksBased on 1 called-in Priority 2 events with a recorded arrival. Counts this small can swing from one week to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of kidnap calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
0
—
—
Week of Jul 6
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
104.8 min
104.8 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 3 Calls Averaged 105 Minutes to Get an Officer Over the Last 12 WeeksBased on 1 called-in Priority 3 events with a recorded arrival. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
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 week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
0–5 min
30–60 min
1–4 hr
Week of Jun 15
3
100.0%
—
—
—
Week of Jun 22
1
—
100.0%
—
—
Week of Jun 29
0
—
—
—
—
Week of Jul 6
2
50.0%
—
50.0%
—
Week of Jul 13
0
—
—
—
—
Week of Jul 20
0
—
—
—
—
Week of Jul 27
0
—
—
—
—
Week of Aug 3
0
—
—
—
—
Week of Aug 10
1
—
—
—
100.0%
Week of Aug 17
0
—
—
—
—
Week of Aug 24
0
—
—
—
—
Week of Aug 31
0
—
—
—
—
14% of Called-In Events Took Over an Hour Over the Last 12 WeeksThat is 14% of 7 called-in events. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of kidnap calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
0–5 min
Week of Jun 15
3
100.0%
—
Week of Jun 22
1
—
100.0%
Week of Jun 29
0
—
—
Week of Jul 6
1
100.0%
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
0% of Priority 1 Calls Took Over an Hour Over the Last 12 WeeksThat is 0% of 5 called-in Priority 1 events. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of kidnap calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
30–60 min
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
0
—
Week of Jul 6
1
100.0%
Week of Jul 13
0
—
Week of Jul 20
0
—
Week of Jul 27
0
—
Week of Aug 3
0
—
Week of Aug 10
0
—
Week of Aug 17
0
—
Week of Aug 24
0
—
Week of Aug 31
0
—
0% of Priority 2 Calls Took Over an Hour Over the Last 12 WeeksThat is 0% of 1 called-in Priority 2 events. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of kidnap calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
1–4 hr
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
0
—
Week of Jul 6
0
—
Week of Jul 13
0
—
Week of Jul 20
0
—
Week of Jul 27
0
—
Week of Aug 3
0
—
Week of Aug 10
1
100.0%
Week of Aug 17
0
—
Week of Aug 24
0
—
Week of Aug 31
0
—
100% of Priority 3 Calls Took Over an Hour Over the Last 12 WeeksThat is 100% of 1 called-in Priority 3 events. Counts this small can swing from one week to the next.
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.
“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. “n=” under each month is the number of events logged that month 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.
“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. “n=” under each week is the number of events logged that week 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.