Report an error
Burglaries in Oregon correlates with...
Variable | Correlation | Years | Has img? |
Popularity of the first name Brian | r=0.98 | 38yrs | No |
Popularity of the first name Jennifer | r=0.98 | 38yrs | No |
Popularity of the first name Crystal | r=0.97 | 38yrs | No |
Popularity of the first name Ashely | r=0.97 | 38yrs | No |
Popularity of the first name Katie | r=0.97 | 38yrs | No |
Popularity of the first name Amy | r=0.96 | 38yrs | No |
US average milk-fat content of frozen dairy products | r=0.96 | 22yrs | No |
Milk consumption | r=0.95 | 32yrs | No |
Viewership count for Days of Our Lives | r=0.93 | 37yrs | Yes! |
Google searches for 'snoop dog' | r=0.91 | 19yrs | No |
The divorce rate in Oregon | r=0.9 | 23yrs | No |
The marriage rate in Oregon | r=0.87 | 23yrs | No |
Burglaries in Oregon also correlates with...
<< Back to discover a correlation
You caught me! While it would be intuitive to sort only by "correlation," I have a big, weird database. If I sort only by correlation, often all the top results are from some one or two very large datasets (like the weather or labor statistics), and it overwhelms the page.
I can't show you *all* the correlations, because my database would get too large and this page would take a very long time to load. Instead I opt to show you a subset, and I sort them by a magic system score. It starts with the correlation, but penalizes variables that repeat from the same dataset. (It also gives a bonus to variables I happen to find interesting.)