✅ Rust server guide

Running a Rust server: the admin's setup checklist

Starting a Rust server is easy; running one people stay on takes some groundwork. Work through this list before your first wipe and you'll avoid the problems that sink most new servers.

8 min read · Updated October 2026 · Free guide for Rust server owners
✅ Launch checklist
✓server.cfg & tags set
✓Admins added + writecfg
✓RCON password rotated
✓Oxide / Carbon installed
✓Backups scheduled
✓Rules & tickets ready

1. The basics in server.cfg

  • server.hostname — your server's name, with region, rates and wipe schedule.
  • server.maxplayers — be realistic; a full small server beats an empty big one.
  • server.worldsize and server.seed — map size and layout. Smaller maps feel busier.
  • server.description, server.headerimage, server.url and server.tags — what players see in the browser.
  • server.saveinterval — how often the world saves.

2. Add yourself and your staff

Give admin rights with ownerid <steamid> "name" "reason" (full admin) or moderatorid <steamid> "name" "reason" (moderator), then run server.writecfg so it's saved. Use each person's own Steam ID — never share one admin account.

Skip the manual work.PlayerAnalytics does this automatically on your Rust server — try it free for 14 days.
Start free trial →Live demo

3. RCON, securely

RCON lets you run console commands remotely. Set a long, random rcon.password, don't share it in Discord, and change it whenever a staff member leaves. Fewer people with RCON is safer.

4. Oxide or Carbon

To run plugins you need a modding framework — Oxide (uMod) or Carbon. Install it after each Rust update (the monthly update replaces the server files), and keep your plugins updated with it.

5. Backups

Back up your save files, plugin configs and data folders regularly — at minimum before every update and every wipe. A server that loses a week of progress to a bad update loses players with it.

6. Rules and staff

  • Write short, clear rules: group limit, what counts as griefing, cheating policy, how to appeal.
  • Show them to players when they join and pin them in Discord.
  • Pick staff you trust, give them their own accounts and roles, and keep a log of moderation actions.

7. Support and anti-cheat

Decide how players report problems before you need it — a ticket system, not DMs to the owner. Read our guides on catching cheaters and setting up tickets.

8. Know your server

Watch how many players return, when you're busiest and what they actually do. It's the difference between guessing and knowing what to change.

Tip: Most new servers fail on consistency, not features: a reliable wipe time, staff who answer, and quick action on cheaters will beat any plugin list.

How PlayerAnalytics helps

PlayerAnalytics covers the “after setup” part in one plugin and dashboard: player stats and leaderboards, cheat detection with evidence, tickets across Discord and in-game, a web RCON console with an audit log, staff roles, moderation with a Discord mod log, server-down alerts and retention analytics — configured on the website, not in config files.

Questions

How do I make myself admin on a Rust server?

Run ownerid <your steamid> "name" "reason" in the server console, then server.writecfg to save it. Use moderatorid for moderators.

Do I need Oxide or Carbon?

Only if you want plugins. Vanilla Rust runs without them, but almost every community server uses one for admin tools, stats and quality-of-life features.

How often should I back up my Rust server?

At least before every update and wipe, and ideally daily.

Your server, without the guesswork.

Everything in this guide — tracked, flagged and handled for you by PlayerAnalytics.

$9.99 per server / month after the trial · Oxide & Carbon · cancel anytime

More guides