Report an error
Popularity of the first name Maximillian correlates with...
| Variable | Correlation | Years | Has img? |
| The number of cooks, short order in North Carolina | r=0.95 | 20yrs | No |
| US average milk-fat content of milk fat and skim solids byproduct fluid beverage milk | r=0.95 | 22yrs | No |
| The divorce rate in Kentucky | r=0.95 | 23yrs | No |
| Global iPod Sales | r=0.95 | 9yrs | No |
| US birth rates of triplets or more | r=0.95 | 20yrs | No |
| GMO use in cotton | r=0.94 | 23yrs | No |
| Petroluem consumption in Portugal | r=0.93 | 43yrs | No |
| The divorce rate in Wisconsin | r=0.92 | 23yrs | No |
| Petroluem consumption in Greece | r=0.91 | 43yrs | No |
| Pirate attacks globally | r=0.9 | 14yrs | No |
| US average milk-fat content of cottage cheese | r=0.9 | 22yrs | No |
| Arson in Iowa | r=0.87 | 22yrs | No |
| Google searches for 'report UFO sighting' | r=0.87 | 19yrs | No |
| Ticket sales for Cleveland Guardians games | r=0.82 | 45yrs | No |
Popularity of the first name Maximillian 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.)
