How to Set Up a Rust Server

Running your own Rust server is the best way to control who plays, what rules apply, and how the map wipes. This guide covers setting one up on a provider's server, from install through your first wipe schedule.

QUICK ANSWER

Rent a Rust server through a provider like RUST, pick the Rust template so it installs automatically, then set your world size and seed before first launch since those lock in the map. Run ownerid with your Steam ID64 to grant yourself admin, use the built in console commands for moderation, and set up a weekly wipe schedule through the panel so the map refreshes on its own.

Fact

Rust servers are almost always run on a rented provider rather than a home PC, since the game needs steady CPU power that most home internet and hardware cannot match under load.

Fact

World size and seed only apply at server start, so changing them later forces a full map wipe.

Fact

Auth level 2, granted through ownerid, is permanent admin access that survives server restarts.

Requirements and install

Pick a provider server for this, RUST works well since Rust needs real CPU and RAM to run a full map without lag. Home PCs usually cannot keep up once a wipe fills the map with bases.

1Order a plan through your provider.
2Log into the game panel once the server spins up.
3Select the Rust template if it is not already preselected. Most providers preinstall it automatically.
4If it is not preinstalled, use the one click install button under the game selection screen.

Check current PRICE options if you have not picked a plan yet. No SteamCMD or manual downloads needed on a panel.

Server config: world size, seed, max players

Open the panel's config editor or startup settings tab before your first launch. These settings only apply on server start, so set them now.

1Set worldsize to control the map diameter in meters. Use 3000 to 4000 for small to medium groups, or 4500 and up for bigger communities.
2Set seed to control the map layout. Leave it blank for a random map, or enter a specific seed if you already have one you like.
3Set maxplayers to your expected player cap. Set it a bit above your peak so you are not turning people away during busy hours.

Changing world size or seed later forces a fresh wipe, since the map itself changes.

Granting yourself admin (auth levels)

Rust has three auth levels. Level 2 is full admin, level 1 is moderator, level 0 is a regular player.

1Connect to the server once so your Steam ID gets logged.
2Find your Steam ID64 through your Steam profile URL or a Steam ID lookup site.
3Open the server console through the panel and run:

ownerid YOUR_STEAM_ID64 YOUR_NAME

This grants level 2 permanently, even after restarts. Use moderatorid the same way for level 1 instead.

Essential admin and moderation commands

Run these from the server console for day to day moderation.

1kick "player name" removes someone without a permanent ban.
2ban steamid or banid steamid blocks a player from reconnecting.
3unban steamid reverses a ban.
4teleportpos x y z or teleport2me "player name" moves players around.
5giveto "player name" itemname amount spawns items into a player's inventory.
6server.writecfg saves your current settings so changes stick after a restart.

Check your panel for built in kick, ban, and restart buttons first, since most providers cover the basics without needing the raw console.

Wipe schedules and what each wipe clears

Set your wipe type based on what you want to reset.
A full wipe clears the map, all bases, inventories, and blueprints. Run this weekly for the standard reset most communities use.
A map only wipe keeps blueprints and skill progression, but generates a new map and clears bases and items. Use this for a shorter cycle between full wipes.
A blueprint wipe resets crafting progress back to basic recipes. Pair this with a full wipe on a monthly schedule, matching Rust's own monthly forced updates.
Set your schedule through the panel's cron style scheduler under server settings so wipes run automatically.

Sizing for player count

Match your plan to your expected player count.

1For 10 to 50 players, an entry tier plan with a few CPU cores and 8 GB of RAM is enough.
2For 50 to 100 players, use 6 or more cores and 16 GB of RAM, since entities and bases add up fast over a wipe cycle.
3For over 100 players, move to a high end plan built for Rust, since the game leans on single core performance. Check DED plans once you scale past a casual friend group.

Add Oxide once your server is stable for admin tools, custom commands, and extra features. See our guide on Rust plugins with Oxide for the setup walkthrough.

FAQs

Do I need to install anything myself on a provider server?

Usually not. Most panels preinstall Rust when you pick the Rust template, or offer a one click install if it is not automatic.

How do I make myself admin on my Rust server?

Connect to the server once, then run ownerid with your Steam ID64 and name through the console. This grants full admin permanently.

How often should I wipe my server?

A weekly full wipe is the most common schedule. Larger or more casual communities sometimes stretch it to every two weeks, while competitive servers may wipe more often.