MasaApps360
English
RCON

Rust RCON on your phone: connect and run admin commands

Rust does not use the older Source format that most RCON clients expect; it runs WebSocket RCON instead, so a plain RCON client just sits there and times out. Start the server with +rcon.web 1, an rcon.port (28016 by default) and an rcon.password, then add it in the RCON app with Rust as the server type. The app switches to WebSocket on its own, and status, say, global.kick and the rest go out from your phone.

3 min read · Updated 2026-09-15

Download on the App Store

Why Rust needs a different protocol

Most games speak Source RCON over a plain TCP socket. Rust's web RCON runs over a WebSocket, full stop, which is exactly why a generic RCON client so often fails against a Rust server. Choose Rust under Server Type in this app and it sets the Protocol to WebSocket for you. There is nothing left to switch by hand.

Turning RCON on at the Rust server

This part lives in your server's start command or config file, nowhere near the app. The usual set of flags:

  • +rcon.web 1 to enable the WebSocket RCON.
  • +rcon.port 28016 (or the port your host assigns).
  • +rcon.password "your-long-password".

Restart it and wait until the map has actually finished loading. A server still mid-startup will not answer RCON yet, no matter how patient you are with the connect button.

Pointing the app at your Rust server

  1. Tap the plus button on Servers to open Add Server.
  2. Fill in Server Name and Hostname or IP.
  3. Open Server Type and pick Rust. The Port becomes 28016 and Protocol shows WebSocket on its own.
  4. Enter your rcon.password into RCON Password, exactly as it appears in your start command.
  5. Tap Test Connection, then Save Server.
  6. Tap the server to open the console, and the very first line there tells you whether the connection went through.

Everyday commands to reach for

Everyday Rust RCON commands
CommandWhat it does
statusServer status and the list of connected players
say Restart in 5 minutesBroadcasts a message to everyone
global.kick PlayerName reasonKicks a player
global.ban PlayerName reasonBans a player
global.unban 7656...Removes a ban by Steam ID
server.saveForces a world save
server.writecfgSaves the current server settings
server.fpsShows the server's current frame rate

These and plenty more show up in Command Suggestions as you type, arguments included, so you are not stuck memorising exact spelling at 2am.

A wipe day routine

The console's Macros screen hides a Rust Wipe Day template under Templates, a common one to install on a server. It sends a warning with say, runs server.save and server.writecfg, sends a final message and saves again, 60 seconds between each step. 5 commands, 4 minutes total. Tap Install to copy it, then edit the wording to sound like your own community.

Building your own instead: tap New Macro, add each command under Commands (executed in order), set Delay between commands, and leave the console open until it finishes. The commands leave from your phone one at a time, not all at once.

When the Rust connection just will not go

  • Connection refused usually means RCON is not enabled, or you typed the game port (28015 by default) where the RCON port should go.
  • A few seconds of nothing, then a timeout, points at a firewall or the host blocking the RCON port. Check it with Port Scanner and the Rust preset, which runs through 28015, 28016 and 28082 at once.
  • Logged in fine but commands do nothing at all: the server may still be loading the map. Give it a minute and try status again.

Questions and answers

What is the default Rust RCON port?
28016, usually, one above the 28015 game port. Plenty of hosts assign their own anyway, so trust whatever your provider or start command actually shows.
Where do I find the Rust RCON password?
Whatever follows +rcon.password in your start command, or the matching field in your host's control panel. The app has no way of fetching that for you, it only knows what you type in.
Can I switch a Rust server back to Source RCON?
The app follows the server type you pick, not the other way round. Rust means WebSocket, because that is what current Rust servers expect regardless. Choose a different server type and the protocol switches along with it.
Does the app show the Rust console log live?
No, you only see the reply to each command you actually send, never a live feed of chat or the server log itself.

You might also like

More RCON guides