Configure Rust’s Query Port for In‑Game Browser Visibility

To make your Rust server appear in the in‑game browser you must configure a distinct query port in addition to the game port, and forward both correctly.

To make your Rust server appear in the in‑game browser you must configure a distinct query port in addition to the game port, and forward both correctly. Without a separate query port the server can accept players but remains invisible in the browser list.\ \

Why a Separate Query Port?\

Rust uses server.port for player connections (UDP) and server.queryport for server‑information queries and browser listings (UDP)【https://topofgames.info/guides/rust-query-port-not-working/】. Valve retired query‑port sharing in February 2023, making a unique query port mandatory for visibility【https://topofgames.info/guides/rust-query-port-not-working/】. If server.queryport is omitted, Rust automatically selects max(server.port, rcon.port)+1【https://topofgames.info/guides/rust-query-port-not-working/】, which can accidentally match the game port and break browser visibility.\ \

How to Configure Ports\

Command‑line configuration\

You can launch the server with explicit ports:\n``\nRustDedicated.exe +server.port 28015 +server.queryport 28017 +rcon.port 28016\n``\nThe plus signs are required; order does not matter. Typical defaults are 28015 (game), 28017 (query), 28016 (RCON).\n\

server.cfg overrides\

Create or edit rust/server/<identity>/cfg/server.cfg. Settings here override any command‑line arguments at startup【https://topofgames.info/guides/rust-query-port-not-working/】. Example:\n``text\nserver.port 28015\nserver.queryport 28017\nrcon.port 28016\n`\nNote the omission of the leading +`.\ \

Port‑forwarding checklist\

1. Forward server.port as UDP.\
2. Forward server.queryport as UDP and ensure it differs from the game port【https://topofgames.info/guides/rust-query-port-not-working/】.\
3. Forward rcon.port as TCP (separate from the UDP ports)【https://topofgames.info/guides/rust-query-port-not-working/】.\
4. Verify each port from outside using a scanner or by connecting directly.\

\

Validation steps\

• Startup log – look for the line Server startup complete before testing connectivity【https://topofgames.info/guides/rust-query-port-not-working/】.\
• LiveGameServerList – refresh the in‑game browser; the server should now appear.\
• SteamCMD – run status after a few minutes; the query port should be listed with the visibility flag.\

\

Common pitfalls\

• Using the same number for both game and query ports – change one; they must differ.\
• Forgetting UDP forwarding for the query port – the server will stay hidden.\
• Conflicting settings between command line and server.cfg – remember server.cfg wins.\
• Not restarting after changes – the server must reload to apply new ports.\

\

FAQ\

What happens if I omit server.queryport?\ Rust calculates it as max(server.port, rcon.port)+1, which may equal the game port on some setups, breaking browser visibility.\ \ Can I use the same port for query and game on a shared host?\ No. Valve requires a distinct query port; otherwise the server will not appear in the browser.\ \ Should the query port use TCP?\ No. The query port must use UDP; using TCP results in query failures.\ \ For deeper troubleshooting see the full guide: https://topofgames.info/guides/rust-query-port-not-working/

Sources and verification

• Rust Query Port Not Working: Fix Server Browser VisibilityExplains port roles, default calculation, retirement of query-port sharing, and provides a practical checklist for configuring and validating Rust query ports.
• Creating a server - Rust WikiProvides official syntax for server.port, server.queryport, rcon.port, command‑line examples, and server.cfg precedence.