Rust Server CheckerPOCKET TOOLKIT
01 / DIAGNOSTICS
Inspect the query endpoint, player count, and Steam listing from one place.
Use a hostname or IP. Add one target per line.
CURRENT CHECK
03 / REFERENCE
Run live diagnostics from the hosting server, or inspect a saved capture.
Inspect an older JSON/JSONL capture or offline analysis. Imported results are labeled as saved captures.
01 / LIVE
Enter up to eight targets on the Check tab and select Run probe. Results reflect the hosting server’s network, which may differ from your game client’s connection.
For local use, clone the repository and run with Python 3.10 or newer:
python3 server.py
Open 127.0.0.1:8765. Steamworks providers require a local Steam runtime; key-based Steam providers require STEAM_WEB_API_KEY in the server environment. Unavailable providers are reported separately.
02 / IMPORT
Import a JSON run, a watch capture in JSONL, or the output of offline incident analysis. Files are read in your browser.
python3 rust_server_checker.py rust.example.com@28017 --json > report.json
python3 rust_server_checker.py rust.example.com@28017 --watch 10 --count 6 --jsonl watch.jsonl
python3 rust_server_checker.py --analyze watch.jsonl --json > analysis.json
03 / TARGETS
Use label=host:game_port@query_port. Omit the ports to try common Rust query ports. Specify @QUERY_PORT for servers using other ports; an IP may host several servers. Put an IPv6 address in brackets when supplying a game port.
EU=[2001:db8::1]:28015@28017
04 / SIGNALS
A2S shows query reachability. Steam registration and Steam client enumeration have separate results. RCON reports TCP reachability. Player rows appear when the server returns them.