Post-apocalyptic scrap metal survival base compound at sunset
Rust servers· Nodes online

Rust servers that hold up on wipe day

High-clock CPUs, NVMe storage, and enough memory for a 4K map with a full population. Oxide and Carbon plugin support, scheduled wipes, and instant provisioning.

  • No setup fees
  • Cancel anytime
  • Stripe & PayPal

Straightforward pricing

Memory sets the price at $1.25 per GB per month. CPU cores and NVMe storage scale with the memory you pick, and you can resize any time.

Small server
PvE / community, 2500 map
$10.00/month
  • 4 CPU Cores
  • 8 GB RAM
  • 80 GB NVMe
+ DDoS & premium support: $12.00/mo
+ Managed by a technician: $16.00/mo
Order Small server
Standard wipe
Popular
3000-3500 map, 50-100 players
$20.00/month
  • 6 CPU Cores
  • 16 GB RAM
  • 160 GB NVMe
+ DDoS & premium support: $24.00/mo
+ Managed by a technician: $32.00/mo
Order Standard wipe
Full pop
4000+ map, 150 players & plugins
$30.00/month
  • 8 CPU Cores
  • 24 GB RAM
  • 240 GB NVMe
+ DDoS & premium support: $36.00/mo
+ Managed by a technician: $48.00/mo
Order Full pop

Built for rust servers

High-clock CPU

Rust's entity simulation punishes slow cores. We run modern high-frequency CPUs with real headroom so tick rate holds when the map fills up.

NVMe map storage

Map generation, save files, and procedural terrain load fast on enterprise NVMe — shorter boot times after every restart and wipe.

Population that scales

Move the RAM slider before wipe day and drop back afterwards. Prorated invoices mean you only pay for the size you actually need.

DDoS protection

Competitive Rust servers get attacked. Always-on layer 3/4 filtering plus an enhanced tier with priority support during incidents.

Custom maps & seeds

Upload a .map file, set a levelurl, or dial in world size and seed from the startup variables — no ticket needed.

Managed plugin help

Our managed tier installs Oxide, resolves plugin conflicts after Facepunch updates, and configures your gather rates and kits.

How much RAM do you need?

SetupPlayersRecommended RAMFrom
PvE / small community, 2500 map20-408 GB$10.00 / mo
Standard vanilla wipe, 3000 map50-8012 GB$15.00 / mo
Modded 3500 map with plugins80-12516 GB$20.00 / mo
Large 4000+ map, full pop150+24 GB$30.00 / mo

Rust memory use grows with map size, entity count, and time since the last wipe — a month-old 4000 map with thousands of bases uses far more than a fresh one. Budget one size above your target population if you run long wipe cycles.

Launching your Rust server

  1. Pick a RAM size based on your intended map size and population from the table above.
  2. Set world size, seed, server name, description, and max players in the panel startup variables.
  3. Install Oxide or Carbon from the egg settings, then upload your plugins over SFTP or the file manager.
  4. Configure gather rates, kits, and permissions in the oxide/config folder, then restart to apply.
  5. Schedule your wipe and restart tasks from the panel scheduler — the control panel guide covers cron syntax and backup tasks.

Wipe cycles and performance

Facepunch pushes a mandatory update on the first Thursday of every month, which force-wipes blueprints roughly quarterly and breaks plugin compatibility until authors publish updates. Plan a short maintenance window that day.

Between wipes, server memory climbs as players build. If you see rising frame times late in the cycle, prune decayed entities, lower the entity render distance, and check for plugins that poll every tick.

Backups run on your schedule and cover the map, blueprint, and identity files — take one before every update so a bad plugin never costs you a wipe.

Questions, answered

How much RAM does a Rust server need?

Rust is memory hungry. A 3000-size map with 50 players wants around 12 GB, a 4000 map with 100+ players is comfortable at 16-24 GB, and small community or PvE servers can run on 8 GB.

Do you support Oxide / uMod and Carbon?

Yes. Install Oxide (uMod) or Carbon from the panel egg settings, then drop plugin .cs files into the oxide/plugins folder — they hot-load without a restart.

How do wipes work?

You control them. Use the panel scheduler to delete map and blueprint files on your own cadence — most servers run forced wipes on the first Thursday of the month when Facepunch pushes an update.

Can I run a custom map?

Yes. Upload a .map file over SFTP or point the levelurl startup variable at a hosted custom map, then set your world size and seed in the startup tab.

Will my server show in the community browser?

Yes. Your server registers with the Rust master list on boot; set server.description, header image, and tags from the startup variables so it presents correctly in the browser.

What happens on Facepunch force-wipe day?

Rust updates on the first Thursday of each month. Update your server from the panel once the client patch lands, wipe the map, and restart — managed customers can have us run the update and plugin compatibility pass instead.

Do you protect against DDoS attacks?

Every node sits behind always-on layer 3/4 filtering. The enhanced tier adds tuned protection and priority support during an attack, which matters for competitive Rust servers.

Can I resize mid-wipe?

Yes. Move the RAM slider, approve the prorated quote, and the new limits apply to your running server without touching your map or blueprint data.

Ready when you are

Configure RAM, protection, and managed help — your server provisions as soon as the first invoice is paid.

Build my server