Check whether a Rust server answers the Steam query that the in-game browser and server lists use, with players, map and response time.
Checked from our server on the public internet. We don't store the addresses you check or any player names. Private and local addresses are refused.
Rust answers Steam's A2S server query over UDP. Players connect on the game port (28015 by default), but the query goes to the query port, which Facepunch documents as one more than the higher of server.port and rcon.port: 28017 with the defaults. Set +server.queryport to fix it explicitly.
Online or not, players and maximum, the server name, the map (for example Procedural Map) and the round-trip time. Queued players and player names are not shown.
Type the address players use (ip:28015). We try the documented query-port candidates and report the one that answered.
server.queryport) as well as the game port.server.port or rcon.port moved the query port. Enter the query port directly in the port field if the default guess misses.More on query ports and what a status check can and can't tell you in the basic mode guide, and everything ServerStats tracks on Rust servers.
Enter the address players use, including the game port. We query it from the public internet the way the server browser does, so a green result means players can see it.
By Facepunch's rule it is one more than the higher of server.port and rcon.port, which is 28017 with the defaults of 28015 and 28016. You can set it yourself with +server.queryport.
The usual causes are a closed UDP query port, a server that is still loading, or a query port that moved because you changed server.port or rcon.port.
Yes. ServerStats basic mode checks the same query around the clock, keeps player history across wipes and posts to Discord when the server stops answering. Free for one server; the Rust plugin adds server FPS, entities and wipe analytics.
Basic mode runs this check continuously for one server, keeps the history and alerts you in Discord when it goes down.