How to Ban or Unban a Player on a Rust Server (SteamID64 Commands)

For a reliable Rust server ban, use the player’s SteamID64: banid <SteamID64> "<reason>". To remove it, run unban <SteamID64>. You can issue these commands in the in-game F1 console, an RCON connection, or your host’s web console, but your account must have server-admin rights. Use banlistex to verify the result. Because community guides disagree about some argument order and command aliases, run help on the server you operate before applying a command at scale.

Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.

Quick reference

What you need before issuing a ban

• A valid SteamID64. This is the dependable identifier for both offline bans and unbans. Display names can change and are not a durable key.
• An authorized account. Commands are rejected or ignored when issued by a normal player. Rust servers use auth levels; community administration guides describe levels above 0 as administrator access.
• A command channel. You can use the F1 console while connected, a remote-console (RCON) session, or the console supplied by your hosting panel. RCON and a web console are useful when you are not in the game.
• A reason and a record. Add a concise reason to the ban where your server’s syntax permits it, and keep an external moderation log with the SteamID64, date, moderator and evidence.

The exact command parser can vary with the server build and the administration layer. The syntax below reflects the form most community guides agree on; treat the server’s own help output as authoritative.

#	Preview	Product	Price
1		Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key...	$25.00	Buy on Amazon
2		Rust Video Game Notebook	$15.00	Buy on Amazon
3		Rust Game Props Large Furnace (S)	$14.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

How to ban a player by SteamID64

1. Open an authorized console

1. In the game, press F1 to open the developer console, or connect through RCON or your host’s web console.
2. If the command is refused, stop and check your auth level rather than repeatedly submitting it. An administrator or owner must grant the account rights first.

2. Enter the SteamID64 form

Use the following pattern, replacing the angle-bracketed values:

banid <SteamID64> "<reason>"

For example, the structure is a 17-digit SteamID64 followed by a quoted reason; do not copy a sample ID from another server. A reason is optional in the commonly documented form, but including one makes later review and appeals easier.

#1 Best Overall

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

• Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
• High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
• Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
• Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
• NOT a sticker*

$25.00

Buy on Amazon

3. Resolve the argument-order conflict safely

Not every guide presents banid identically. One documented form is banid <SteamID64> "<reason>"; another inserts the player name, as in banid <SteamID64> "<name>" "<reason>". Before relying on the second form, run help banid (or the general help command if subcommand help is unavailable) and follow the usage line returned by your server. Do not assume that an accepted command used the intended fields: verify the resulting entry with banlistex.

4. Check the response

Read the console response for an error, an unknown command message, or a confirmation. A successful-looking response is not enough if the player can reconnect; immediately inspect the ban list and, if necessary, test with a controlled reconnect.

How a name-based ban differs

A name-based ban can target a player who is currently connected. The server can read that connection’s SteamID and associate the ban with it. This method is not suitable for an offline player: once the connection is gone, the server cannot reliably resolve a display name to the person you intend to block.

Because no universal name-ban command is established across community syntax, do not paste an invented command from a different server configuration. In the F1, RCON or web console, run help, identify the name-targeting ban command your build exposes, and execute it while the player is still online. Then run banlistex and confirm that the listed SteamID64 and, where shown, name match the intended account.

How to inspect the current ban list

Use banlistex

Run:

banlistex

Community guides describe this command as listing banned users and showing names and reasons when those fields were recorded. Treat the output as the authoritative check for your running server, especially after a syntax variation or a name-based action.

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

Check the saved ban file

Bans are also written to a file in the server’s configuration area. The exact location depends on how the server is installed and which identity folder it uses; one commonly cited layout places bans.cfg under the server identity folder. Use your panel’s file manager or the host’s documented server directory to locate the active file rather than editing an unrelated copy.

Keep a backup of the ban file before making manual changes or server upgrades. Community administration guides warn that a crash before a normal shutdown or save can lose a newly issued ban. A dated backup lets you restore the list without reconstructing every SteamID64 from memory.

How to unban a player

1. Obtain the SteamID64

The unban operation requires the SteamID64, not the player’s current or former display name. If the person is listed, copy the identifier from banlistex or from the moderation record you kept when the ban was issued.

2. Run the unban command

In F1, RCON or the hosting-panel console, enter:

unban <SteamID64>

Community instructions generally show the ID without quotation marks. Replace the placeholder with the digits only; do not add the player’s name or a reason unless your server’s own help output explicitly documents extra arguments.

3. Verify removal

Run banlistex again. The entry should no longer appear as an active ban. If it remains, inspect the console for a spelling or permission error, confirm that you are connected to the intended server instance, and repeat the command using the exact usage displayed by help unban.

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

4. Restore administrative access when applicable

If the banned account was an administrator or moderator, banning it removes its auth level immediately. After a successful unban, the account must be granted its previous level again; unbanning alone does not restore permissions.

Where each command can be run

The command itself is not made safer by changing interfaces. The same SteamID64, permission check and local syntax rules apply in F1, RCON and a web console.

Granting admin rights when commands are rejected

Only an authorized account can run ban commands. Community server guides document these rights commands:

• ownerid <SteamID64> "<name>" "<reason>"
• moderatorid <SteamID64> "<name>" "<reason>"

After granting a role, run:

server.writecfg

A reconnect is often needed before the new permissions take effect. Community summaries describe moderator level 1 as allowing actions such as kicking, banning, muting and teleporting; the owner level also unlocks convars and item spawning. Those capability descriptions are not a substitute for your server’s own permission output, so use help and a harmless test command to confirm the role you intend to assign.

Common failures and precise fixes

“Unknown command” or no response

• Run help in the same console to see whether your build uses the command without a prefix or with global., such as global.banid.
• Confirm that you are connected to the Rust server console, not a shell or a panel field that accepts only startup parameters.
• Check your auth level. A moderator or owner assignment may not apply until you reconnect.

The command is accepted but the wrong player is affected

• Recheck every digit of the SteamID64. Do not rely on a similar display name.
• For a name-based action, confirm that the intended player was online at the moment of execution.
• Run banlistex and compare the recorded name and ID before taking further action.

The player reconnects after a ban

• Inspect banlistex to determine whether the ban was actually recorded.
• If the list is empty, repeat the command using the exact banid usage shown by help; argument order is the most frequently documented variation.
• Check that you did not issue the command to a different server instance through RCON or a hosting panel.
• Review the saved ban file after a clean save. A crash before shutdown or save can discard a newly added entry, which is why a backup is recommended.

An unban does not let the player return

• Verify the exact SteamID64 and run banlistex again.
• Make sure the account is not covered by another administrative system or a separate server instance; the Rust command removes the matching Rust ban only.
• If the account previously held admin rights, restore them separately with the appropriate ownerid or moderatorid command and save with server.writecfg.

A guide tells you to use banid for an unban

One host page has been reported to display banid in its unban section. That conflicts with the otherwise consistent unban <SteamID64> syntax and should be treated as a documentation error unless your own server’s help unban output says otherwise.

A dependable moderation workflow

1. Identify the account. Prefer the SteamID64. If the player is online and you only have a name, use the server’s documented name-ban command while the connection is active, then capture the ID shown in the ban list.
2. Record the decision. Note the SteamID64, display name at the time, reason, moderator, timestamp and any evidence. This prevents a later name change from obscuring the case.
3. Apply the action. Use F1, RCON or the panel console and follow the local help syntax, including any required name field.
4. Verify immediately. Run banlistex; do not assume that a command-line acknowledgement equals a persistent ban.
5. Save and back up. Run the server’s normal save procedure, use server.writecfg when changing auth assignments, and keep a backup of the active ban file.
6. Handle appeals by ID. When lifting a ban, confirm the SteamID64, run unban, verify the list, and separately restore administrative privileges if the account had them.

Key distinctions to remember

Rust administration commands are community-documented; no single official Facepunch command reference is provided. For that reason, the safest practice is to treat help on the live server as the final authority, verify every ban with banlistex, and preserve the ban file so a crash or syntax mistake does not erase your moderation record.

Quick Recap

Bestseller No. 1

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.; NOT a sticker*

$25.00

Bestseller No. 2

Rust Video Game Notebook

$15.00

Bestseller No. 3

Rust Game Props Large Furnace (S)

Acrylic Painting Pla Plastic

$14.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.