Minetrack Data

Background

Over the last several years Minetrack has been busy pinging a selection of Minecraft servers every few seconds. The resulting databases being a time series collection of each included Minecraft servers reported player count. Those databases have now been published into the public domain and made available for download. I have published these databases because although niche, very few long term collections of this type of data exist, and far fewer made public.

Feel free to contact me with questions, or neat things you did with the data: hello@minetrackdata.nklow.com

Want to make your own database? Minetrack is open source: github.com/Cryptkeeper/Minetrack

Schema

Each database is a .sql file, as generated by SQLite. Besides any pruning, all databases have been released in their original schemas and have not been optimized for analysis or publishing.

• Each database has two indexes already defined (pre-built by Minetrack).
• The playerCount column will store a 0 value if Minetrack failed to ping the server. Unforunately, this means you cannot differentiate between erroneous pings and playerCount values that happen to be 0.
• The timestamp column is a unix epoch time in milliseconds denoting when the ping response (or error) has been handled.
• Some Minecraft servers may have only been tracked for a portion of the database's full date range.

CREATE TABLE pings (timestamp BIGINT NOT NULL, ip TINYTEXT, playerCount MEDIUMINT);
CREATE INDEX ip_index ON pings (ip, playerCount);
CREATE INDEX timestamp_index on PINGS (timestamp);