The short answer
Steam can only query around 10,000 servers at a time, and Rust hides empty servers from the browser by default. A new server with nobody on it therefore fails both filters at once. Get the first players on by direct connect, keep uptime continuous, and use query caching so your server answers fast enough to stay in the batch.
Key points
- Not being listed is normal for a new server. It is not a fault.
- There are more Rust servers than the query system can reach. Some are always invisible.
- Empty servers are hidden on purpose. Players are the entry ticket, not a reward for it.
- Restarting repeatedly makes the problem worse, not better.
- Direct connect always works and is how you break the loop.
Why the browser hides your server
The Rust server browser is not a directory. It is the result of a query process with hard limits, and understanding those limits is what stops this feeling arbitrary.
Steam has a maximum query ceiling of around 10,000 servers. That is how many it can ask for details at once. Because there are considerably more Rust servers than that in existence, it is physically impossible to see all of them, and there is no setting on your side that changes the arithmetic.
Steam also tries to best-match servers for each player rather than returning a straight list. In practice that matching is unpredictable, and whether a particular server appears for a particular person is close to a lottery.
The empty server problem
Facepunch improved the browser by hiding all empty servers by default. From a player's point of view this is a clear win: the list fills with servers that have people on them rather than hundreds that do not.
From a new server owner's point of view it creates a circular problem. Your server is empty, so it is hidden. It is hidden, so nobody finds it. Nobody finds it, so it stays empty.
Players can tick Show Empty to see everything, but that reverts them to the older, less useful browser, and very few people do it. You cannot build a strategy on the assumption that they will.
The practical consequence: your first few players are worth more than your next hundred. They are what makes the server eligible to be seen at all. Getting three friends to idle on a fresh wipe is not padding the numbers, it is the mechanism by which real players can find you.
How query caching changes it
You cannot raise Steam's ceiling. What you can change is how well your server performs inside the query process it is subject to.
Our anycast A2S network caches query responses across more than 50 points of presence in Europe, America and Asia. When a browser asks about your server, the answer comes from the nearest cache rather than travelling to the server and back. Two things follow:
- Faster responses
- A server that answers quickly is far less likely to be dropped from a query batch for timing out, particularly during busy periods.
- Lower displayed ping
- The ping shown in the browser reflects the distance to the cache, so players anywhere in the world see a low number rather than a discouraging one.
The caching is included on all our shared game hosting automatically, and can be applied through the firewall manager on our VPS, VDS and dedicated servers.
To be clear about what this does and does not do: caching affects the query response, which is discovery. Once a player connects they talk to the server directly at the real network distance. It makes you easier to find, not faster to play on.
Things worth checking first
Before assuming it is the query system, rule out the handful of configuration problems that produce identical symptoms.
- Query port reachable
- The browser talks to the query port, players talk to the game port. A server can be perfectly joinable and completely invisible if only one of the two is open.
- Server name
- If you are searching by name, search for an exact substring. Rust's search is less forgiving than people expect.
- Right tab
- A modded server does not appear under Community. If you run Oxide or uMod, look under Modded.
- Uptime
- Continuous uptime helps. If you have been restarting to test settings, stop, leave it running, and check again in a few hours.
What actually gets you listed
-
Get players on by direct connect
Share the IP and port with anyone you can. Once there are players, the empty server filter stops working against you.
-
Advertise where players look on wipe day
Just-wiped listing sites, the Rust subreddits and Discord wipe channels all reach people actively hunting for a new server. Our Rust server advertising guide covers the specifics.
-
Leave it running
Resist the urge to restart repeatedly. Uptime is one of the few inputs you genuinely control.
-
Use query caching
It removes the response-time reason for being dropped from a batch, which is the part of the problem no amount of advertising fixes.
-
Ask your regulars to favourite it
A favourited server appears in the Favorited tab regardless of the browser. Your existing players then never have to find you again.
Direct connect in the meantime
Nothing about the browser affects direct connection. Anyone with the address can join at any time, listed or not.
client.connect 123.456.78.9:28015Press F1 in Rust, select the CONSOLE tab, paste that with your own address and press Enter. Put it in your Discord, put it on your listing entry, and pin it. For a server that is not yet visible, that line is your entire acquisition funnel, and it is worth treating as such.