Game server hosting
Your own Rust server on AMD Ryzen 7 7700 in Germany or EPYC 4244P in New York. Ready in minutes.
Facepunch's wiki gives 12GB as the figure to build on, and notes a 6k map needs more again. Population and map size both drive it.
A small map and a small population. Below Facepunch's stated 12GB figure, so size up if you grow.
$10/month
Matches the 12GB Facepunch asks for. The sensible starting point.
$12/month
A larger map or a busier server with headroom to grow.
$16/month
Full-size map, heavy population, modded.
$24/month
Most Rust hosting pages are a year out of date on how the server uses your CPU.
192GB DDR5. The main simulation loop still rewards fast cores.
High-clock Zen 4 in North America too.
Facepunch's UsePlayerUpdateJobs reached default tier 3 in July 2026, with tier 4 experimental now.
Forced wipe lands first Thursday, 19:00 London. We apply the update and the wipe for you.
Facepunch has profiled its own servers at 350-360 players. We do not cap slots.
Full SFTP for plugin frameworks and configs, plus RCON for live administration.
12GB of free RAM, according to Facepunch’s own wiki — and more again for a 6k map.
Facepunch attaches an important caveat: “These values are not fixed and highly depend on the use case and population of the server.” There is no official per-map-size RAM table, so any host quoting you “3k map equals X GB, 6k equals Y GB” has made those numbers up. The two variables that actually move it are world size and how many people are building.
Both now — which is a change from a couple of years ago.
Rust’s main simulation loop still benefits from high single-thread performance, so clock speed matters most. But Facepunch has progressively moved player updates, snapshot serialisation and networking onto worker threads, and as of July 2026 that work is on by default. Entity saving is being parallelised too. A modern Rust server makes real use of additional cores, unlike a Valheim or Palworld server.
The first Thursday of every month at 19:00 London time, when Facepunch ships its monthly update.
Facepunch has committed publicly to monthly updates on the first Thursday, and the update forces a map wipe. The server-side wipe timer defaults match that schedule and can be set to weekly or biweekly instead. Blueprint wipes are a separate question — Facepunch has explicitly not committed to wiping blueprints every month. We apply the update and the wipe for you.
| Item | Official value |
|---|---|
| RAM | 12GB free, and a 6k map will use more |
| Storage | 15GB free disk, SSD/NVMe highly preferred |
| CPU | No model or clock published. Only: the more players, the faster your CPU needs to be |
| Player limit | +server.maxplayers. No hard cap documented; Facepunch profiles its own at 350-360 |
| World size | +server.worldsize, 1000 to 6000. Larger maps need more RAM and disk |
| Ports | 28015 UDP game, query UDP, RCON TCP, Rust+ companion TCP |
| Operating system | Windows, Linux or macOS |
| Wipe cycle | Forced map wipe first Thursday of each month, 19:00 London |
Source: Facepunch’s official Rust server wiki , plus Facepunch devblogs for the threading and wipe details.
Common questions about running a Rust server with us.
Refund within 72 hours if it isn't for you.
Humble AI, our team and the Discord are a message away.
