About Rust Data
One table, every public Rust server, refreshed on a five-minute interval. Here is where the fields come from.
The in-game browser gives you a name and a number and little else, so Rust Data keeps a wider row: player count, queue, map seed, FPS, entity count, wipe schedule and the tags a server publishes about itself. Two sources feed it. The first is Steam's public Rust server list, which supplies names, player counts, queues and tags. The second is a direct query to each server for the fields Steam does not carry. Not every server answers a direct query, so some rows hold Steam data only and the remaining fields stay empty rather than being guessed.
Population history is kept as a time series, one sample per refresh, so you can compare a server's weekday average against its post-wipe spike instead of judging it by the current count. Rankings use players over the past week, hour by hour; a server that holds a population every evening outranks one that fills for a single night. Order is by player count, never by payment. Start from the full server list, the live player count or the wipe schedule.
Rust Data is independent and not affiliated with Facepunch Studios; nothing here is endorsed by them. Server names, descriptions and images belong to the people who run those servers. Where a field looks wrong, the usual cause is the server's own configuration, and a corrected value appears within about one refresh interval. If it does not, write to hello@rustdata.space. The programme is described on the advertising page, and the rules for using the data are in the terms.