For a small private Rust group, the best starting point is a vanilla dedicated server with a 4,000-size procedural map, 10 player slots, a fixed seed, separate game, query, and RCON ports, and a long unique RCON password. Install or update the server with SteamCMD, put the server identity and world choices in the startup command, and keep recurring values in server/<identity>/cfg/server.cfg. This gives you a predictable baseline without adding plugin maintenance.
Use one configuration layer for each key while you set the server up. The Facepunch wiki and Oxide documentation do not agree on whether command-line values or server.cfg win when both define the same setting, so avoid duplicates and verify the effective value on the running server. Vanilla Rust does not provide gather-rate or loot multipliers; a 2x or 5x progression server requires a mod framework and a plugin.
Which Rust server settings matter most for a small group?
Identity, map generation, capacity, network ports, and administration determine whether the server starts reliably and feels right for your players. Cosmetic fields such as the name and description can be changed later, but the world seed and size should be chosen before people begin building.
Identity and data location
The +server.identity value is both the server’s internal name and the directory name used for its saves, configuration, logs, and other data. For example, an identity of group1 creates a data path such as server/group1/. Keeping a distinct identity makes backups and multiple worlds easier to manage.
World and player capacity
server.level selects the map type; the official worked example uses Procedural Map. server.seed controls procedural generation. Facepunch documents seeds from 0 through 2,147,483,647 and a world-size range of 1,000 through 6,000. Larger maps consume more disk space and memory, while additional concurrent players increase CPU demand.
| Setting | What it controls | Documented range or example | Small-group starting point |
|---|---|---|---|
server.level |
Map type | Procedural Map in the official example |
Procedural Map |
server.seed |
Procedural terrain generation | 0–2,147,483,647 | Choose and record a fixed value, such as 1234 |
server.worldsize |
Map width and overall world area | 1,000–6,000 | 4,000 for the official small-group example |
server.maxplayers |
Maximum simultaneous players | 10 in the official example | 10, then raise only after checking resources |
A 4,000 map and 10 slots are editorial starting values drawn from Facepunch’s example, not a performance guarantee. A weak host or a very small group may be better served by a smaller world. If you add plugins or increase the slot limit, watch CPU, memory, and storage use before expanding the map.
How do I install or update a Rust dedicated server?
SteamCMD is Facepunch’s documented installation and update method. Rust’s dedicated-server App ID is 258550.
- Install SteamCMD on the machine that will run the server.
- Create a separate server directory so the installation, identity data, and backups are easy to find.
- Run SteamCMD and log in anonymously, then set the installation directory and install or update App ID
258550. - Leave SteamCMD available for later updates; the same command updates the server files without changing your identity directory.
- Create your startup script in the server directory and test it once before inviting players.
When you update Rust, stop the server cleanly first. If you use Oxide, update the framework after every Rust update; the Facepunch guidance says an Oxide update follows server updates and must be applied each time. A startup script that runs SteamCMD can replace modified files with vanilla files, so check the script before relying on it for a modded server.
What should I put in the Rust startup command?
Put choices that identify and generate the world, expose network services, and set the initial presentation in the RustDedicated launch command. This compact baseline combines the official example with a separate query port:
-batchmode
+server.identity "group1"
+server.level "Procedural Map"
+server.seed 1234
+server.worldsize 4000
+server.maxplayers 10
+server.port 28015
+server.queryport 28017
+rcon.port 28016
+rcon.password "REPLACE_WITH_A_LONG_UNIQUE_SECRET"
+rcon.web 1
+server.hostname "Our Rust Group"
+server.description "Private group server"Understanding each argument
-batchmoderuns the dedicated server without an interactive graphical window, which is useful for a headless machine.+server.identityselects the data directory and internal identity.+server.level,+server.seed, and+server.worldsizedefine the generated world.+server.maxplayerssets the slot ceiling.+server.portaccepts player connections.+server.queryportserves browser queries and must not be the same UDP port asserver.port.+rcon.port,+rcon.password, and+rcon.webenable remote administration in the form shown by the official example.+server.hostnameand+server.descriptioncontrol what players see in the server list and connection window.
Replace the sample identity, seed, name, description, and password. Treat the RCON password as a full administrator credential: do not reuse a personal password or publish it in a chat, screenshot, or public script.
What belongs in server.cfg?
RustSetups documents server/<identity>/cfg/server.cfg as the persistent configuration file and says it is read at every boot. Put recurring values there when you want them reapplied after restarts.
server.hostname "Our Rust Group"
server.description "Private group server"
server.maxplayers 10Most edits to this file take effect on the next restart. Some console variables can be changed while the server is running through RCON, but a restart is the dependable way to apply file edits and confirm that the saved configuration is valid.
How should I avoid command-line and file conflicts?
Define each key in one place during initial setup. The Facepunch wiki and Oxide guide give conflicting precedence guidance for a command-line value versus a value in server.cfg; the exact order is therefore not established here. If you need to change a value, remove the old duplicate, restart, and inspect the effective value in the server console or through RCON rather than assuming which layer won.
Which ports and RCON settings should I use?
Rust uses separate services for player traffic, server-browser queries, and remote administration. Keep the ports distinct and use the protocol documented for each service.
| Setting | Purpose | Example | Protocol or requirement |
|---|---|---|---|
server.port |
Player connections | 28015 | UDP in the Facepunch example |
server.queryport |
Server-browser queries | 28017 in the sample above | UDP; must differ from server.port |
rcon.port |
Remote console administration | 28016 | Use a dedicated port and a strong password |
rcon.password |
Authenticates RCON access | A long, unique secret | Keep it private and rotate it if exposed |
rcon.web |
Enables the web mode shown in the official example | 1 |
Use the mode required by your RCON client |
Changing the game port means players must use the new port when connecting. Changing the query port affects browser discovery rather than the player connection endpoint. Record all three values in your server notes so a restart or host migration does not leave administrators guessing.
How do I change settings safely and make them stick?
Use this change-and-check cycle whenever you modify a world, capacity, or network value.
- Stop the Rust server cleanly and wait for the process to exit.
- Back up the complete
server/<identity>/directory, including saves and configuration. - Edit either the startup command or
server.cfg; do not define the same key in both while troubleshooting. - Start the server and watch the console for parsing errors, port conflicts, or a failed world load.
- Connect locally or through your normal RCON tool and query the effective value.
- Check the server browser name and description, then have one group member connect before announcing the new address.
RustSetups also places plugin JSON files under oxide/config/ or carbon/configs/. Include those directories in your backup when the server is modded. A complete identity-directory backup lets you restore the world and settings together instead of recovering individual files.
Do gather rates, loot multipliers, and stack sizes need plugins?
Yes. The cited vanilla configuration reference does not provide convars for gather-rate or loot multipliers. A server advertised as 2x, 5x, or otherwise boosted needs a mod framework such as Oxide or Carbon plus a plugin that changes gathering, loot, or stack behavior.
Vanilla configuration
Map type, seed, world size, slots, hostname, description, ports, and RCON are core server settings. They can be managed with the dedicated-server command and server.cfg without a mod framework.
Modded progression
Install the framework supported by your server build, then add only the plugins you need. Keep plugin configuration files separate from core settings, document every change, and test after updates. Plugins can increase CPU or memory use, so recheck resource headroom before raising server.maxplayers.
Facepunch warns that an update process can restore files to vanilla. After every Rust update, confirm that the framework and plugins are still present and compatible before allowing players to join.
Should I self-host or rent a managed Rust server?
Self-hosting is best when you want direct shell and file control and are comfortable maintaining SteamCMD, ports, backups, updates, and RCON. A managed host is easier when you prefer a control panel, automated operations, support, and a provider-maintained network. Neither choice changes the underlying Rust settings; it changes who operates the machine.
| Decision area | Self-hosting | Managed hosting |
|---|---|---|
| Control | Direct access to files, startup scripts, ports, and operating-system settings | Panel-managed settings, with access depending on the plan |
| Capacity | You choose the machine’s CPU, memory, storage, and network limits | Choose a plan and upgrade when its advertised resources or slots are insufficient |
| Mod support | You install and update Oxide or Carbon and their plugins | Check whether the host supports the framework and plugin installation you need |
| Operations | You schedule updates, wipes, backups, monitoring, and recovery | Many providers offer panels, automated backups, DDoS protection, scaling, and support; verify each feature |
| Location and latency | Place the machine where you can reach it and where your connection allows | Select the available region closest to the group and confirm the upgrade path |
| Cost | Uses your existing hardware, electricity, bandwidth, and time | Recurring monthly fee; compare the included CPU, RAM, storage, slots, backups, and support |
Hosting plans change frequently. A June 11, 2025 comparison from TechRadar reports materially different resource limits and management features among providers, so verify current specifications, region availability, mod support, and pricing before paying. Choose on control, resources, mod compatibility, operations, location, and total cost rather than on player-slot count alone.
What are the most common setup failures?
The server starts with an unexpected value
Look for the key in both the launch command and server.cfg. Because precedence documentation conflicts, remove one definition, restart, and query the live value. Also confirm that you edited the file under the identity actually used by +server.identity.
The server is visible but players cannot join
Confirm that the player connection uses server.port, not the query or RCON port. Check that server.queryport is a different UDP port and that your host or provider has made the selected ports available. If you changed ports, distribute the new connection details to the group.
Remote administration does not work
Verify the RCON port, password, and web-mode setting in the running server. A typo in the password or using the player port in an RCON client will fail even when the game server itself is healthy. Replace the credential if it has appeared in a public log or message.
The world loads slowly or the server struggles at peak time
Reduce server.worldsize or server.maxplayers before adding more plugins. Facepunch specifically links larger worlds with higher memory and disk requirements and more concurrent players with greater CPU demand. Compare resource use during normal play, not only while the server is empty.
Plugins disappeared after an update
Check whether an automated SteamCMD step restored vanilla files, then reinstall or update Oxide or Carbon and verify the plugin configuration directory. Do not restore plugins blindly over a newer Rust build; confirm framework compatibility first.
What is a sensible final checklist for a private group?
- SteamCMD installs App ID
258550in a dedicated directory. - The identity is named and its backup path is known.
- The level, fixed seed, world size, and slot limit match the group’s expectations.
- The player port and query port are different UDP ports.
- RCON has its own port, a long unique password, and the required web mode.
- Persistent values are in
server/<identity>/cfg/server.cfgwithout conflicting duplicate definitions. - The complete identity directory and, for modded servers, plugin configuration directories are backed up.
- Oxide or Carbon and every plugin are checked after each Rust update.
- One player completes a connection test before the whole group switches over.
Frequently Asked Questions
Do I need RCON to run a private Rust server?
No. RCON is a remote administration service, not a prerequisite for the game server itself. You can operate a small server locally, but RCON is useful when the machine is headless or you need to change supported console variables without opening the server window.
What should I check before increasing the player limit?
Watch CPU use during busy fights and base-building, memory while the world is loaded, and available disk space for saves and updates. If plugins are installed, test with them enabled because their overhead is part of the real capacity you are trying to support.
Why does my browser listing show a different name after a restart?
The running process may be reading a different identity directory or another configuration layer may be redefining server.hostname. Confirm the +server.identity path, remove duplicate hostname entries, restart, and inspect the effective value.
Can a managed host still use my own server.cfg?
Usually the panel exposes an equivalent configuration editor or file manager, but the exact access varies by provider and plan. Confirm that you can reach the identity directory, retrieve backups, set separate query and RCON ports, and install the framework your group expects before ordering.