Secure client portal

Ports & Server List

RUST Ports Explained (28015 Game, Query, RCON)

Open Rust ports right: 28015/UDP game, separate query UDP, and keep RCON 28016/TCP private.

RUST listens on server.port (wiki 28015/UDP), a separate query UDP port, and rcon.port (commonly 28016/TCP). Chapter22 egg 35 wires these via Startup variables.

Port table

ServicePortProtocolPublic?
Game (server.port)Primary allocation (wiki 28015)UDPYes — players
Query (server.queryport)Egg default 28017UDPYes — server browser
RCON (rcon.port)Egg default 28016TCPNo — private
Rust+ app (app.port)Egg default 28082TCPOptional / private

Managed hosting (Chapter22)

  1. Open Pterodactyl → your RUST server → Network / Startup.
  2. Note SERVER_PORT (game), QUERY_PORT, RCON_PORT, and APP_PORT allocations.
  3. Players connect with game IP:port (client.connect); favorites/list need the query port reachable.
  4. Keep RCON and Rust+ off the open internet when possible.

Node may remap away from 28015/28016/28017 — always copy live allocations. Tip: Egg 35 FRAMEWORK supports vanilla|carbon|oxide (Oxide-capable).

DIY / self-hosted readers

DIY readers: allow game+query UDP and keep RCON allowlisted. See Linux ports and port forwarding explained.

Egg verification (Chapter22)

Egg 35 (Rust): SERVER_PORT game; QUERY_PORT default 28017; RCON_PORT 28016; APP_PORT 28082 (Rust+); FRAMEWORK vanilla|carbon|oxide (Oxide-capable). Wiki 28015/16/17 not pre-seeded on node — remapped at provision.

Facepunch query note

When query is unset, Facepunch uses 1 + max(server.port, rcon.port). Chapter22 sets QUERY_PORT explicitly (default 28017).



Frequently Asked Questions

What is server.port?

Game traffic (wiki default 28015/UDP). On Chapter22 it is the primary SERVER_PORT allocation — copy from Pterodactyl.

Query port formula?

Facepunch: when unset, query is 1 + max(server.port, rcon.port). Egg 35 sets QUERY_PORT default 28017 and RCON_PORT 28016 explicitly.

Is RCON public?

No. Keep rcon.port (default 28016/TCP) private; prefer the panel console.


Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.

Chapter22 RUST hosting

Deploy a managed RUST server.

Chapter22 RUST hosting is Oxide-capable on Pterodactyl—Scrap, Raid, and Wipe tiers in Ogden, UT.