How Rust Browser tracks servers
Rust Browser combines server responses with observed wipe and population history. Use the data to compare places to play, and check the server owner's rules before joining.
Player counts and freshness
Player counts describe the latest successful response, rather than everyone who played during the day. Scanning frequency varies with server rank and activity. A server can change between scans; check the last response time on its detail page. A missing response does not by itself prove that a server has closed.
Detected wipes and predicted wipes
A detected wipe is an observation in our wipe history. A predicted next wipe is an estimate from the available schedule and history, and can change. Forced updates and owner decisions can override the usual timing. A map wipe does not necessarily reset blueprints. The owner's description and rules are separate from our detected and predicted dates.
Server overview timestamps use UTC. The interactive calendar shows times in your browser's local timezone. The just wiped list includes detected map wipes from the last 24 hours.
Population across a wipe
Population retention compares average daily peak population across the analyzed wipe with its opening daily peak. It is a population comparison, not a measurement of whether the same individual players returned. Map population measures average daily peak players per square kilometre of map area. Queue time describes the share of analyzed history buckets with more than ten queued players.
Read these values alongside the number of analyzed wipes and their update time. Limited history and gaps in observations can make comparisons less representative. The history chart helps show how population changes between wipe day and later sessions.
Tags, location and team size
Tags and parsed server information help organize the directory, but cannot describe every rule or modification. A Vanilla tag can appear alongside a boosted gather rate. A solo limit describes the reported maximum group size, rather than how the owner enforces teaming rules. Hosting country is an estimate and does not guarantee your ping.
Use solo servers, vanilla servers or the region lists as starting points, then check the individual server.
Choosing a server
The default directory sorts by current player count. Rank combines population and retention, with category adjustments and a boost for servers carrying the Rust Premium tag. It is not an endorsement or a guarantee of moderation quality. Training and minigame tags are excluded by default and can be included through the filters.
For rules, support and schedule announcements, use the owner's website or Discord linked on the server page. Rust Browser is an independent directory and is not affiliated with Facepunch Studios.