Over the last 12 months, 453 crimes were reported in Fauntleroy & Seaview — about 29.3 per 1,000 residents per year. Counts include only offenses that carry a location in the public data, so they understate violent crime. There are also 83 traffic crashes in the same window and 66 open building violations on record nearby.
Check a specific Fauntleroy & Seaview address — free, no account needed:
Crime is compared per resident (rate); counts are totals for the area. Other figures are compared to the average Seattle neighborhood.
Over the last 12 months, 453 crimes were reported in Fauntleroy & Seaview — about 29.3 per 1,000 residents per year. Counts include only offenses that carry a location in the public data, so they understate violent crime.
Enter any Fauntleroy & Seaview address in the search box above to see block-level crime, violations, and crashes for that exact location — free.
Directly from the City of Seattle open-data portal, updated automatically.
Get a free preview report — permits, safety, zoning, and more for one address — and set up weekly change alerts. No account required to start.
Search Fauntleroy & SeaviewCrimes cover the Fauntleroy & Seaview Community Reporting Area (the boundary outlined on the map), over the last 12 months. Crime is compared per resident (rate), so a large, busy area can have a high total but a lower rate; crash and violation counts are compared to the average Seattle neighborhood. Source: City of Seattle open data (data.seattle.gov). SPD withholds the location of sensitive offenses: about 36% of violent offenses over the last six months (nearly all rapes and homicides, about a third of aggravated assaults, and one in six robberies) carry no location in the public data, so they cannot be placed near an address. The University of Washington campus is policed by UWPD and is not covered by this feed. Counts here include only offenses with a location and understate violent crime. The Port of Seattle Police (Sea-Tac and the seaport) and the King County Sheriff’s Office (Boeing Field) have their own jurisdictions and are not in this feed. SDOT back-fills collision records for about three months, so crash counts end 90 days before the latest record and the newest collisions are not yet included. The feed has no property-damage-only collisions in recent months, so counts are not comparable to cities that publish them. Open data updates on a delay, so the most recent records may be incomplete. For general information only — not legal, financial, or real-estate advice.
Outline shows the Fauntleroy & Seaview Community Reporting Area; figures count records inside it. Search an address for block-level detail.