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

Harbor (Water)

Harbor (Water) calls over time: volume, outcomes, and response speed

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

Swipe sideways to see the full chart →
06001,2002009: 109 harbor (water) calls logged in CAD2010: 197 harbor (water) calls logged in CAD2011: 180 harbor (water) calls logged in CAD2012: 181 harbor (water) calls logged in CAD2013: 210 harbor (water) calls logged in CAD2014: 259 harbor (water) calls logged in CAD2015: 348 harbor (water) calls logged in CAD2016: 457 harbor (water) calls logged in CAD2017: 424 harbor (water) calls logged in CAD2018: 405 harbor (water) calls logged in CAD2019: 579 harbor (water) calls logged in CAD2020: 596 harbor (water) calls logged in CAD2021: 545 harbor (water) calls logged in CAD2022: 642 harbor (water) calls logged in CAD2023: 687 harbor (water) calls logged in CAD2024: 1,044 harbor (water) calls logged in CAD2025: 772 harbor (water) calls logged in CAD2026: 631 harbor (water) calls logged in CAD2009n=1092011n=1802013n=2102015n=3482017n=4242019n=5792021n=5452023n=6872025n=7722026n=631
harbor (water) calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodHarbor (water) calls logged in CAD
2009109
2010197
2011180
2012181
2013210
2014259
2015348
2016457
2017424
2018405
2019579
2020596
2021545
2022642
2023687
20241,044
2025772
2026631
Harbor Calls Are Down 26% From Their 2024 PeakSeattle Police logged 1,044 harbor calls in 2024 and 772 in 2025, the most recent full year.

Harbor: 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: 0.9%2009 · Report taken, no arrest: 7.3%2009 · Resolved on scene: 81.7%2009 · Unable to locate: 4.6%2009 · Other (unfounded / cancelled): 5.5%2010 · Arrest / citation: 0.5%2010 · Report taken, no arrest: 14.7%2010 · Resolved on scene: 70.6%2010 · Unable to locate: 11.2%2010 · Other (unfounded / cancelled): 3.0%2011 · Arrest / citation: 2.8%2011 · Report taken, no arrest: 19.4%2011 · Resolved on scene: 63.3%2011 · Unable to locate: 9.4%2011 · Other (unfounded / cancelled): 5.0%2012 · Arrest / citation: 2.2%2012 · Report taken, no arrest: 17.1%2012 · Resolved on scene: 63.5%2012 · Unable to locate: 12.2%2012 · Other (unfounded / cancelled): 5.0%2013 · Arrest / citation: 0.5%2013 · Report taken, no arrest: 13.3%2013 · Resolved on scene: 66.2%2013 · Unable to locate: 12.4%2013 · Other (unfounded / cancelled): 7.6%2014 · Arrest / citation: 0.4%2014 · Report taken, no arrest: 12.4%2014 · Resolved on scene: 65.6%2014 · Unable to locate: 12.4%2014 · Other (unfounded / cancelled): 9.3%2015 · Arrest / citation: 0.3%2015 · Report taken, no arrest: 12.4%2015 · Resolved on scene: 75.3%2015 · Unable to locate: 8.9%2015 · Other (unfounded / cancelled): 3.2%2016 · Report taken, no arrest: 10.3%2016 · Resolved on scene: 79.2%2016 · Unable to locate: 8.3%2016 · Other (unfounded / cancelled): 2.2%2017 · Arrest / citation: 1.4%2017 · Report taken, no arrest: 9.7%2017 · Resolved on scene: 80.0%2017 · Unable to locate: 5.9%2017 · Other (unfounded / cancelled): 3.1%2018 · Arrest / citation: 0.7%2018 · Report taken, no arrest: 10.6%2018 · Resolved on scene: 76.8%2018 · Unable to locate: 6.7%2018 · Other (unfounded / cancelled): 5.2%2019 · Arrest / citation: 0.5%2019 · Report taken, no arrest: 10.4%2019 · Resolved on scene: 78.9%2019 · Unable to locate: 6.6%2019 · Other (unfounded / cancelled): 3.6%2020 · Arrest / citation: 0.3%2020 · Report taken, no arrest: 10.7%2020 · Resolved on scene: 80.5%2020 · Unable to locate: 5.9%2020 · Other (unfounded / cancelled): 2.5%2021 · Arrest / citation: 1.7%2021 · Report taken, no arrest: 8.3%2021 · Resolved on scene: 76.7%2021 · Unable to locate: 9.0%2021 · Other (unfounded / cancelled): 4.5%2022 · Arrest / citation: 0.5%2022 · Report taken, no arrest: 20.7%2022 · Resolved on scene: 73.1%2022 · Unable to locate: 3.0%2022 · Other (unfounded / cancelled): 2.8%2023 · Arrest / citation: 0.6%2023 · Report taken, no arrest: 18.8%2023 · Resolved on scene: 74.2%2023 · Unable to locate: 3.8%2023 · Other (unfounded / cancelled): 2.6%2024 · Arrest / citation: 0.7%2024 · Report taken, no arrest: 36.7%2024 · Resolved on scene: 58.3%2024 · Unable to locate: 2.9%2024 · Other (unfounded / cancelled): 1.4%2025 · Arrest / citation: 1.6%2025 · Report taken, no arrest: 25.4%2025 · Resolved on scene: 65.8%2025 · Unable to locate: 4.4%2025 · Other (unfounded / cancelled): 2.8%2026 · Arrest / citation: 1.6%2026 · Report taken, no arrest: 18.4%2026 · Resolved on scene: 70.8%2026 · Unable to locate: 5.4%2026 · Other (unfounded / cancelled): 3.8%2009n=1092011n=1802013n=2102015n=3482017n=4242019n=5792021n=5452023n=6872025n=7722026n=631
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)
20091090.9%7.3%81.7%4.6%5.5%
20101970.5%14.7%70.6%11.2%3.0%
20111802.8%19.4%63.3%9.4%5.0%
20121812.2%17.1%63.5%12.2%5.0%
20132100.5%13.3%66.2%12.4%7.6%
20142590.4%12.4%65.6%12.4%9.3%
20153480.3%12.4%75.3%8.9%3.2%
2016457—10.3%79.2%8.3%2.2%
20174241.4%9.7%80.0%5.9%3.1%
20184050.7%10.6%76.8%6.7%5.2%
20195790.5%10.4%78.9%6.6%3.6%
20205960.3%10.7%80.5%5.9%2.5%
20215451.7%8.3%76.7%9.0%4.5%
20226420.5%20.7%73.1%3.0%2.8%
20236870.6%18.8%74.2%3.8%2.6%
20241,0440.7%36.7%58.3%2.9%1.4%
20257721.6%25.4%65.8%4.4%2.8%
20266311.6%18.4%70.8%5.4%3.8%
“Unable to Locate” Outcomes Are Holding Near 5% of Harbor CallsReport-taken outcomes moved from 10% of calls in 2016 to 18% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Harbor: 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 57% of harbor 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. Because most harbor events are logged by officers, these charts describe only the small share that were called in. 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: 12.1 min2010: 9.5 min2011: 9.0 min2012: 13.2 min2013: 14.6 min2014: 15.6 min2015: 16.6 min2016: 7.0 min2017: 10.7 min2018: 10.1 min2019: 11.4 min2020: 15.2 min2021: 11.6 min2022: 7.9 min2023: 9.7 min2024: 10.1 min2025: 9.0 min2026: 14.9 min2009: 34.8 min2010: 21.5 min2011: 21.1 min2012: 22.1 min2013: 30.7 min2014: 30.7 min2015: 29.9 min2016: 21.9 min2017: 24.0 min2018: 20.8 min2019: 33.4 min2020: 38.6 min2021: 29.3 min2022: 27.6 min2023: 30.9 min2024: 30.7 min2025: 37.8 min2026: 67.0 min2009n=792011n=1272013n=1672015n=1762017n=1622019n=1862021n=3062023n=2202025n=2912026n=271
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
20097912.1 min34.8 min
20101419.5 min21.5 min
20111279.0 min21.1 min
201214413.2 min22.1 min
201316714.6 min30.7 min
201421315.6 min30.7 min
201517616.6 min29.9 min
20161617.0 min21.9 min
201716210.7 min24.0 min
201816310.1 min20.8 min
201918611.4 min33.4 min
202030815.2 min38.6 min
202130611.6 min29.3 min
20222037.9 min27.6 min
20232209.7 min30.9 min
202422910.1 min30.7 min
20252919.0 min37.8 min
202627114.9 min67.0 min
The Average Call Waits 67 Minutes for an Officer to ArriveAs calls rose 69% between 2016 and 2025, average response time has grown about 3-fold in the past 10 years, from 22 minutes in 2016 to 67 in 2026. This counts only the 43% of harbor calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
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.

Harbor: 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 57% of harbor events, because they have no wait. Because most harbor events are logged by officers, these charts describe only the small share that were called in. 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: 29.1%2009 · 0–5 min: 19.0%2009 · 5–30 min: 32.9%2009 · 30–60 min: 11.4%2009 · 1–4 hr: 3.8%2009 · 4–8 hr: 3.8%2010 · No recorded response: 32.6%2010 · 0–5 min: 12.8%2010 · 5–30 min: 40.4%2010 · 30–60 min: 8.5%2010 · 1–4 hr: 5.7%2011 · No recorded response: 29.1%2011 · 0–5 min: 15.0%2011 · 5–30 min: 43.3%2011 · 30–60 min: 6.3%2011 · 1–4 hr: 6.3%2012 · No recorded response: 23.6%2012 · 0–5 min: 16.0%2012 · 5–30 min: 46.5%2012 · 30–60 min: 6.2%2012 · 1–4 hr: 7.6%2013 · No recorded response: 28.7%2013 · 0–5 min: 20.4%2013 · 5–30 min: 34.7%2013 · 30–60 min: 5.4%2013 · 1–4 hr: 9.6%2013 · 4–8 hr: 1.2%2014 · No recorded response: 29.1%2014 · 0–5 min: 23.5%2014 · 5–30 min: 31.9%2014 · 30–60 min: 7.5%2014 · 1–4 hr: 7.0%2014 · 4–8 hr: 0.9%2015 · No recorded response: 31.8%2015 · 0–5 min: 13.1%2015 · 5–30 min: 41.5%2015 · 30–60 min: 8.5%2015 · 1–4 hr: 4.0%2015 · Over 8 hr: 1.1%2016 · No recorded response: 21.7%2016 · 0–5 min: 16.8%2016 · 5–30 min: 49.7%2016 · 30–60 min: 7.5%2016 · 1–4 hr: 3.7%2016 · 4–8 hr: 0.6%2017 · No recorded response: 25.9%2017 · 0–5 min: 16.7%2017 · 5–30 min: 44.4%2017 · 30–60 min: 7.4%2017 · 1–4 hr: 4.9%2017 · 4–8 hr: 0.6%2018 · No recorded response: 27.6%2018 · 0–5 min: 20.2%2018 · 5–30 min: 40.5%2018 · 30–60 min: 6.1%2018 · 1–4 hr: 4.9%2018 · 4–8 hr: 0.6%2019 · No recorded response: 31.7%2019 · 0–5 min: 12.4%2019 · 5–30 min: 38.7%2019 · 30–60 min: 9.7%2019 · 1–4 hr: 6.4%2019 · 4–8 hr: 1.1%2020 · No recorded response: 34.4%2020 · 0–5 min: 10.7%2020 · 5–30 min: 38.0%2020 · 30–60 min: 8.4%2020 · 1–4 hr: 5.5%2020 · 4–8 hr: 1.9%2020 · Over 8 hr: 1.0%2021 · No recorded response: 45.1%2021 · 0–5 min: 10.1%2021 · 5–30 min: 30.7%2021 · 30–60 min: 6.2%2021 · 1–4 hr: 7.2%2021 · 4–8 hr: 0.7%2022 · No recorded response: 40.4%2022 · 0–5 min: 6.9%2022 · 5–30 min: 40.9%2022 · 30–60 min: 5.9%2022 · 1–4 hr: 4.4%2022 · 4–8 hr: 1.5%2023 · No recorded response: 40.0%2023 · 0–5 min: 6.8%2023 · 5–30 min: 35.9%2023 · 30–60 min: 8.2%2023 · 1–4 hr: 8.2%2023 · 4–8 hr: 0.9%2024 · No recorded response: 39.7%2024 · 0–5 min: 9.6%2024 · 5–30 min: 34.1%2024 · 30–60 min: 9.2%2024 · 1–4 hr: 7.0%2024 · 4–8 hr: 0.4%2025 · No recorded response: 38.8%2025 · 0–5 min: 9.3%2025 · 5–30 min: 33.0%2025 · 30–60 min: 9.3%2025 · 1–4 hr: 8.2%2025 · 4–8 hr: 1.4%2026 · No recorded response: 40.6%2026 · 0–5 min: 9.6%2026 · 5–30 min: 29.5%2026 · 30–60 min: 6.6%2026 · 1–4 hr: 10.0%2026 · 4–8 hr: 1.5%2026 · Over 8 hr: 2.2%2009n=792011n=1272013n=1672015n=1762017n=1622019n=1862021n=3062023n=2202025n=2912026n=271
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
20097929.1%19.0%32.9%11.4%3.8%3.8%—
201014132.6%12.8%40.4%8.5%5.7%——
201112729.1%15.0%43.3%6.3%6.3%——
201214423.6%16.0%46.5%6.2%7.6%——
201316728.7%20.4%34.7%5.4%9.6%1.2%—
201421329.1%23.5%31.9%7.5%7.0%0.9%—
201517631.8%13.1%41.5%8.5%4.0%—1.1%
201616121.7%16.8%49.7%7.5%3.7%0.6%—
201716225.9%16.7%44.4%7.4%4.9%0.6%—
201816327.6%20.2%40.5%6.1%4.9%0.6%—
201918631.7%12.4%38.7%9.7%6.4%1.1%—
202030834.4%10.7%38.0%8.4%5.5%1.9%1.0%
202130645.1%10.1%30.7%6.2%7.2%0.7%—
202220340.4%6.9%40.9%5.9%4.4%1.5%—
202322040.0%6.8%35.9%8.2%8.2%0.9%—
202422939.7%9.6%34.1%9.2%7.0%0.4%—
202529138.8%9.3%33.0%9.3%8.2%1.4%—
202627140.6%9.6%29.5%6.6%10.0%1.5%2.2%
The Average Call Waits 15 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 15 minutes in 2026, more than double what it was in 2016. 14% of calls took more than an hour to get a response in 2026, compared with 4% in 2016. This counts only the 43% of harbor calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
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.