WISPDOCK / GAME HOSTING
Rust server hosting
Run a private survival world or build a community around clear rules. Pick the map, seed and wipe schedule before inviting players.
Plan the map and wipes
Rust uses server.seed and server.worldsize for procedural maps. The server.identity keeps a server’s data separate. A larger map or a long-lived world needs more resources than a small fresh map.
Server identity and RCON
Keep the identity directory when backing up. Use a strong, separate RCON password and restrict access. Tell players whether a wipe removes only the map or also blueprints.
Bring your world, keep a copy
Tell us the game version, your mods and whether you already have a save. Keep the original files until you have joined the new server and checked your progress. If something fails, send the first useful error from the startup log with passwords and tokens removed.
Choose the setup before the size
Use the panel to review the plans and regions for this game. Moving a busy world or running a large mod list? Talk it through with us before ordering.
Rust hosting FAQ
Can I add plugins?
Rust plugins need a compatible framework such as uMod or Carbon. Updates can break compatibility, so keep a backup and check the framework and plugin releases before updating a busy server.
How do I get started?
Create a Wispdock account, select Rust and check the available plan, region and full price in the panel. If you are bringing mods or a save, send us the details before choosing.
How should I choose a plan?
For Rust, start with the world, mods and expected activity. A fresh private server and a long-running community have different needs. Ask us about your setup rather than choosing by player count alone.
What should I back up before an update?
Stop the server cleanly, then keep a separate copy of the save, configuration and required mod list. Test the updated server before replacing your only working copy.