Rust server hosting for your wipes and your rules
Run a vanilla, community or modded Rust server on a procedural or custom map, with your own wipe cadence, plugins and rules. Facepunch’s monthly update day stays on your calendar.
- Procedural maps from 1000 to 6000, or a custom map
- Oxide (uMod) and Carbon plugin frameworks
- Browser tags for wipe cadence, mode and region
- Sizes from the 12 GB of RAM Facepunch recommends
- PlayersThere is no fixed limit; Facepunch notes that more players need a faster CPU.
- Set with server.maxplayers
- PortsThe game uses 28015/UDP. RCON uses TCP (often 28016), and the query port defaults to one above the higher of the two.
- 28015 UDP · RCON on TCP
- World size
- 1000–6000 (server.worldsize)
- Forced wipeFacepunch’s monthly update; the default wipe timer points at 19:00 London time.
- First Thursday of every month
- Plugins
- Oxide (uMod) · Carbon
- Anti-cheat
- Easy Anti-Cheat
Server styles
- Vanilla
- Community
- Modded
- PvE
- Custom map
- Rust+
Game facts from Facepunch’s Rust wiki and update notes, checked in October 2026.
- DDoS protection
- 20 game server locations
Rust plans are being prepared
Tell us your expected population, world size and plugins, and our team will reply with the options. Or open a ticket and we will let you know when the plans are online.
How much RAM does a Rust server need?
Rust is one of the heaviest game servers: start from 12 GB and grow with population, world size and plugins.
Find your size
| Feature |
Standard
Up to 50 players, world size up to 3500
|
Recommended Community
Up to 150 players, world size up to 4500
|
High population
150+ players or a 6000 map
|
|---|---|---|---|
| Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore. | 12 GB | 16 GB | 24 GB+ |
| CPU coresFacepunch notes that more players need a faster CPU; clock speed matters more than core count. | 4 | 4–6 | 6+ |
| Disk spaceFacepunch asks for 15 GB of free disk at least; an SSD or NVMe is strongly preferred. | 30 GB | 40 GB | 60 GB |
| Typical use | Vanilla or a small community | A busy community with plugins | Big modded or high-population servers |
-
Standard
Up to 50 players, world size up to 3500
- Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore.
- 12 GB
- CPU coresFacepunch notes that more players need a faster CPU; clock speed matters more than core count.
- 4
- Disk spaceFacepunch asks for 15 GB of free disk at least; an SSD or NVMe is strongly preferred.
- 30 GB
- Typical use
- Vanilla or a small community
-
Recommended
Community
Up to 150 players, world size up to 4500
- Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore.
- 16 GB
- CPU coresFacepunch notes that more players need a faster CPU; clock speed matters more than core count.
- 4–6
- Disk spaceFacepunch asks for 15 GB of free disk at least; an SSD or NVMe is strongly preferred.
- 40 GB
- Typical use
- A busy community with plugins
-
High population
150+ players or a 6000 map
- Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore.
- 24 GB+
- CPU coresFacepunch notes that more players need a faster CPU; clock speed matters more than core count.
- 6+
- Disk spaceFacepunch asks for 15 GB of free disk at least; an SSD or NVMe is strongly preferred.
- 60 GB
- Typical use
- Big modded or high-population servers
Facepunch recommends 12 GB of free memory and 15 GB of disk, more for 6000-size maps. Population, world size and plugins decide the rest.
Maps, plugins and wipes
Shape the server around your community: the map, the rules, the wipe rhythm and how players find you.
Procedural or custom maps
Pick a seed and a world size from 1000 to 6000, or load a custom map from a direct-download link with server.levelurl.
Oxide and Carbon
Community plugin frameworks for kits, admin tools and gameplay changes. Carbon keeps Oxide’s folders and plugin format.
Wipe on your schedule
Set the wipe timer for weekly, biweekly or monthly wipes; Facepunch’s monthly update forces a map wipe anyway.
Browser tags
Tag the wipe cadence, PvE or roleplay style and region in server.tags so the right players find you.
Game modes
Switch server.gamemode to softcore, hardcore or primitive for a different survival experience.
Rust+ companion
With app.port open, players pair the server with Facepunch’s Rust+ app for the map and alerts on their phone.
Set up your Rust server
Four steps to your first wipe day.
-
Pick size and map
Use the table above for your population and world size.
-
Pick a location
Choose the one closest to most of your players from our 20 game server locations.
-
Set identity, seed and tags
Name the server, set server.identity, the seed and the world size, add tags and install Oxide or Carbon if you run plugins.
-
Join the server
Press F1 in Rust and type connect with the address and port, or find the server in the browser.
Other game servers you might like
ARK: Survival Ascended
Crossplay worlds with CurseForge mods, clusters and your own rates.
Learn moreFrequently asked questions
When does Rust force a wipe?
Facepunch releases a monthly update on the first Thursday of every month, and servers have to update with a fresh map. The default wipe timer points at that day, 19:00 London time.
How much RAM does a Rust server need?
Facepunch recommends at least 12 GB of free memory, and more for 6000-size maps. Busy servers with many plugins usually need 16–24 GB.
What world size should I pick?
server.worldsize accepts 1000 to 6000. Smaller maps suit smaller groups and generate faster; large maps need more memory and disk and suit high populations.
Can I use a custom map?
Yes. Put the map file on a direct-download link and set server.levelurl; leave out the world size and seed. Players download the map when they join.
Oxide or Carbon?
Both are community plugin frameworks. Carbon is a drop-in replacement that keeps Oxide’s folders and plugin format, so most plugins work on both. Oxide marks a server as modded by default.
Which ports does a Rust server use?
The game uses 28015/UDP. RCON uses TCP, commonly 28016, and the query port defaults to one above the higher of the game and RCON ports. Rust+ uses app.port, which defaults to 67 above the higher of the game and RCON ports.
How do players connect?
Press F1 to open the console and type connect followed by the address and port, for example connect 203.0.113.10:28015, or use the server browser.
Can I run a PvE or roleplay server?
Yes. Tag the style in server.tags so players find it in the browser, and use server settings or plugins to set the rules you want.
What is a premium server?
Since March 2025 a server can be marked premium with server.premium. Only players with a minimum value of Rust items in their Steam inventory can join, which keeps out throwaway accounts.
Why is my server not listed in the browser?
The query port has to be reachable, and since September 2025 servers started with -insecure are not listed. Keep encryption at its default and check the query port.
Ready for wipe day?
Tell us your population, map and plugins, and we will help you pick the right Rust server.