Rust community servers, measured

Definitions and limits.

1. Population is the count returned at the last refresh, not a daily average.
2. Type is the tab under which the server publishes itself; it is declared, not measured.
3. Tags are self-assigned by owners, so a survival server may carry none and an aim-train server may carry one that was not excluded.
4. Busiest first ranks a snapshot, not a reputation; sort by performance to see sustained population.

A server absent from this table is not necessarily inactive — it may not have been polling at the last refresh, or it may sit in the Modded or Official tab. Region and group limit are not filtered here; the full server browser allows both.

Community servers sit between official servers and modded ones: an owner runs the hardware and sets the wipe cycle and team limit, but core gather rates and loot tables stay at vanilla values. That is why this page is useful for players who want Rust's default economy with a named owner to hold to a schedule.

Three caveats apply to every list built on declared data. First, tab placement is the owner's choice, and the boundary between community and modded is not enforced by measurement. Second, tags are incomplete: the excluded tags remove the obvious training and creative entries, not every non-survival server. Third, an empty server can be new, resting between wipes, or simply quiet; population alone does not distinguish these. For vanilla servers across both community and official tabs, see the vanilla list; for wiping times, see the wipe schedule.