Report an error
Robberies in South Carolina correlates with...
Variable | Correlation | Years | Has img? |
Popularity of the first name Kalyn | r=0.97 | 38yrs | Yes! |
Milk consumption | r=0.96 | 32yrs | Yes! |
Popularity of the first name Sergio | r=0.95 | 38yrs | No |
Popularity of the first name Devin | r=0.95 | 38yrs | No |
Popularity of the first name Jordan | r=0.95 | 38yrs | Yes! |
Popularity of the first name Alex | r=0.95 | 38yrs | No |
Popularity of the first name Jasmine | r=0.95 | 38yrs | No |
Petroluem consumption in Japan | r=0.94 | 38yrs | Yes! |
US birth rates of triplets or more | r=0.94 | 20yrs | Yes! |
Gasoline pumped in Switzerland | r=0.92 | 38yrs | No |
Popularity of the first name Victor | r=0.91 | 38yrs | No |
Ice cream consumption | r=0.9 | 32yrs | No |
The number of university political science teachers in South Carolina | r=0.89 | 20yrs | No |
Robberies in South Carolina 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.)