Short answer: the crime rate for a specific address doesn't really exist. What exists is data aggregated at some geography — a police beat, a ZIP code, a city — and the number you get depends heavily on which one you're looking at. If you want a real answer for the block you're actually buying on, you need to know where the official numbers come from and, more importantly, how to keep them from lying to you by omission.
This isn't the "walk the block, talk to neighbors, check the sex offender registry" article — that's a different piece on this site. This one is about the actual published data: where to find it, and the ways it commonly misleads people who don't know what they're looking at.
Where to actually find crime data
Start with the local police department. Most mid-size and large departments publish their own incident data now, either as a dashboard, a public records portal, or a partnership with a mapping tool. This is the closest thing to a primary source you'll get, because it's the department's own reporting rather than a third party's estimate. Search "[city name] police department crime map" or check the department's website directly — coverage and quality vary a lot by department, so treat "does this city even publish usable data" as itself a signal.
CrimeMapping.com is the tool a lot of departments use to host that data publicly — it's a free, address-searchable map built on feeds from participating agencies (departments like San Jose PD link out to it directly for their own crime stats). If your target city's department isn't on it, that's not necessarily a red flag — plenty of good departments just haven't adopted it.
FBI Crime Data Explorer is the federal aggregator — it pulls agency-reported data into the national Uniform Crime Reporting (UCR) system and lets you compare cities, states, and the national rate. Useful for context (is this city's overall rate higher or lower than the state or national average?), but it tops out at the city/agency level — it doesn't go down to neighborhood or address, and reporting to it is voluntary, so not every agency's data is complete or current in a given year.
Consumer sites like NeighborhoodScout, AreaVibes, and SpotCrime fill the neighborhood-level gap the FBI data doesn't cover — but read the next section before you trust a number from one of these as gospel.
The part that actually matters: how to read it without getting misled
Finding a number is easy. Reading it correctly is the part almost nobody does, and it's the difference between a genuinely useful data point and a decision made off a bad one.
1. "Neighborhood" and "ZIP code" crime rates are usually estimates, not counts
The FBI doesn't publish crime data below the city/agency level, which is why sites like NeighborhoodScout have to derive neighborhood numbers — running the city-wide figure through a proprietary algorithm to estimate a local rate, rather than reporting an actual count of incidents on that street. Data journalist Jeff Asher, who has audited these tools, has flagged that this approach can meaningfully under- or overestimate real local crime, and that ZIP-code-based comparisons are shaky to begin with — ZIP code populations vary enormously (a downtown ZIP built around a stadium or arena can have a tiny residential population but a lot of reported incidents from an entertaining venue full of visitors), so the same raw number can mean wildly different things depending on the ZIP. If a site's crime score for a "neighborhood" doesn't cite an actual incident count from a police department, treat it as a modeled estimate — useful for a general sense, not a precise ranking.
2. Crime is not evenly spread — not even within a "good" or "bad" area
This is the single most important thing to understand, and it's backed by actual criminology, not just intuition. Researcher David Weisburd's "law of crime concentration" — based on studies across multiple cities — found that roughly 2 to 6% of street segments in a given city account for about half of all crime incidents. Crime clusters hard around specific blocks (a bar with a fight problem, an intersection with a string of car break-ins, a particular apartment complex) rather than spreading evenly across a ZIP code or even a named neighborhood.
Practically, this means an aggregated number for "the neighborhood" can be misleading in both directions: a home two blocks from a genuine hot spot can look artificially safe in the aggregate stat, while a home on a quiet, low-crime block inside a ZIP code with one bad corner can look artificially risky. This is exactly why the address-level lookup on your local police department's dashboard or CrimeMapping is worth the extra few minutes over a single "neighborhood score" — it lets you see whether incidents are clustered somewhere specific or actually spread across the area.
3. Violent crime and property crime are not the same number — don't average them
Official crime data splits into two categories, and conflating them is one of the fastest ways to misread a report:
- Violent crime: murder/nonnegligent manslaughter, rape, robbery, aggravated assault — offenses involving force or threat of force.
- Property crime: burglary, larceny-theft, motor vehicle theft, arson — no force against a person, just loss of stuff.
These have very different practical implications for a homebuyer. A neighborhood with elevated property crime — package theft, car break-ins, a garage burglary now and then — is an inconvenience-and-insurance-premium problem. A neighborhood with elevated violent crime is a different category of concern entirely. A single blended "crime index" can hide which one is actually driving the number, so when a site gives you one composite score, dig for the breakdown before you react to it.
4. "High crime" is relative — always check it against a real baseline
A neighborhood can be labeled "above average" while still being objectively safe, if the city or metro it's being compared to is unusually low-crime to begin with. And the reverse is true too — "below the city average" in a city with a genuinely high crime rate can still be worse than the national norm. Don't stop at a single relative label; pull the actual rate (incidents per 1,000 or per 100,000 residents) and compare it against both the city/state figure and the national rate from the FBI's Crime Data Explorer so you know what you're actually being compared to.
A reasonable framework, put together
- Check the local police department's own dashboard or CrimeMapping.com first, and search by the actual address or intersection, not just the neighborhood name — this is your best shot at real incident-level data.
- Pull the city and state numbers from the FBI Crime Data Explorer for context on how the metro compares to state and national averages.
- Separate violent from property crime in whatever you're reading — don't let a single blended score do your thinking for you.
- Treat any neighborhood-level score from a consumer site (NeighborhoodScout, AreaVibes, etc.) as a rough estimate, not a precise ranking, and weight it accordingly.
- Remember that crime concentrates on a small number of blocks — a good aggregate number doesn't guarantee every street is fine, and a mediocre one doesn't mean yours is bad.
None of this replaces actually walking the block at a couple of different times of day — but it means when you do, you'll know what the data can and can't tell you before you get there.
Sources
- FBI Crime Data Explorer
- CrimeMapping.com
- San Jose Police Department — CrimeMapping.com partnership
- NeighborhoodScout
- SpotCrime
- AreaVibes
- Jeff Asher, "ANOTHER Cautionary Crime Data Tale" — on NeighborhoodScout's estimation methodology
- Law of Crime Concentration (Weisburd) — Wikipedia summary of the research
- FBI UCR — violent crime and property crime classifications
- SafeWise — roundup of neighborhood safety tools, checked for current tool landscape