- Rust, Palworld and ARK keep everything players have built in memory, so they need 12–16 GB rather than the 4–8 GB Minecraft gets by on. Four cores are enough, but they should run at 3.5 GHz or faster.
- Satisfactory and Enshrouded fit into 12 GB, Rust, Palworld and a single ARK map ask for 16 GB, and a public 100-player Rust world or an ARK cluster needs 32 GB plus DDoS protection.
- In Russia a suitable plan costs from $19.32 a month for 12 GB, from $23.85 for 16 GB and from $52.84 for 32 GB. That is roughly $232 to $634 a year.
Russia has more than a hundred plans with 16 GB and four cores, but only one in five promises a clock speed of 3.5 GHz or more, and a slow core lags no matter how much memory you have. So the list above only shows plans with a stated clock speed.
Why does clock speed matter more than core count? Most of the work in every game tick runs in one thread. Facepunch's Rust server guide says it plainly: the more players, the faster the CPU needs to be. The Satisfactory wiki admits the game loop is still fundamentally single-threaded, and the ARK wiki puts single-core speed ahead of core count.
Why 8 GB is not enough for these games
Minecraft only keeps the world around its players in memory. These games do not. Rust loads the whole map along with every wall, box and turret players have built. ARK remembers every tamed dinosaur, Satisfactory every conveyor belt, Palworld every Pal at every base. So memory grows not with the number of people online, but with how much they have built since the world started.
Enshrouded is the odd one out. On an empty world it uses about 4.4 GB, each player adds up to 100 MB, and according to the developer it should not go past 6 GB. For 16 players, though, Keen Games recommends a CPU running at 3.7 GHz or faster. Also, the dedicated builds of Enshrouded and ARK: Survival Ascended are Windows-only, and Windows itself eats memory, so 8 GB is tight for them and 12 GB is about right.
In ARK every map in a cluster runs as a separate process, and Empower Servers counts 16 GB or more for each one.
Which setup do you need?
Two things decide it: which game and how many people play at once. Even in the same game, a co-op world for friends and a public world differ in load several times over.
Co-op for your own group
This is a Satisfactory factory for four or an Enshrouded world for a group of up to 16.
- 4 cores at 3.5 GHz+
- 12 GB RAM
- NVMe 50 GB+
- IPv4
Satisfactory lets four players in by default, and an early factory is fine on 8 GB. By the late game, when belts stretch across the map, the save grows and hosts recommend up to 16 GB. A 12 GB plan gives you that headroom for the first months. For Enshrouded, most of the same 12 GB goes to Windows.
A 16 GB server
This is Rust with plugins for up to 50 players, Palworld for 10–20 people or a single ARK map.
- 4 cores at 3.5 GHz+
- 16 GB RAM
- NVMe 80 GB+
- IPv4
For Rust with plugins and 26–50 players, Minestrator names 16 GB, and Sparked Host gives the same for 30–100 people. Palworld officially asks for the same 16 GB and warns that on 8 GB it will start but crash more often from running out of memory.
Going from 12 to 16 GB costs about $4.50 a month, roughly $54 a year. If in doubt, take 16 GB straight away: moving a lived-in world takes an evening and may change the IP address your players have saved in their favourites.
A public project with 100 slots
This is public Rust for a hundred players, a cluster of several ARK maps or Palworld for 32 people.
- 6+ cores at 3.5 GHz+
- 32 GB RAM
- NVMe 150 GB+
- DDoS protection
For 100–200 Rust players Sparked Host recommends 24 GB, and the next step most hosts offer is 32 GB. Palworld for 32 people belongs here too: the developer calls more than 32 GB the stable amount.
Someone will eventually try to flood a public 100-player world with junk traffic, most often on wipe night, so you need DDoS protection that filters UDP, not just websites.
Data table
| Server | Plans | Minimum | One in four cheaper than | Median | Year, min–median |
|---|---|---|---|---|---|
| 12 GB, 4 cores · NVMe 50+ | 10 | $19.32 | $27.08 | $48.72 | $232–$585 |
| 16 GB, 4 cores · NVMe 80+ | 15 | $23.85 | $47.51 | $76.16 | $286–$914 |
| 32 GB, 6 cores · NVMe 150+ · DDoS | 7 | $52.84 | $75.24 | $99.99 | $634–$1,200 |
I would pick from the dark part of each bar: up to $27.08 for 12 GB and up to $47.51 for 16 GB. Above that you pay for extra disk or a famous name, not a shorter tick. If some of your players live in Europe, the same 16 GB at 3.5 GHz or faster costs from $16.83 there. How price tracks memory in general is shown in "VPS prices in 2026".
Why Rust crashes in week three
Right after a wipe Rust uses 4–6 GB, and two weeks later, once players have built their bases, it goes past 12 GB. So size memory for the end of a wipe, not the start. Map size adds to it: per Sparked Host, a fresh 4000 map takes about 6 GB, a 6000 map 8.5 GB.
Rust's forced wipe comes with the game update on the first Thursday of every month, and you cannot skip it: without the update players cannot connect. Palworld has no wipes, but it leaks memory the longer it runs, and hosts such as XGamingServer and ComputeBox advise restarting it every 6–12 hours or at least every night. I will show how to schedule the restart in step 6.
Where a plan for a heavy game lets you down
Once a plan has enough memory, check five more things, each visible on the host's page or on the first evening.
- The CPU clock speed is not stated
Out of 127 Russian plans with 16 GB and four or more cores, 67 give no clock speed at all and 16 run below 3 GHz.
How to tell: the page mentions neither "GHz" nor a CPU model like Ryzen 9, EPYC 9004 or Xeon Gold. Ask support before you pay.
- Exactly as much memory as the game asks for
Facepunch asks for 12 GB of free memory, meaning on top of what the system uses. On a plan with exactly 12 GB, Rust hits the ceiling by week three of a wipe and crashes in the middle of the evening.
How to tell:
journalctl -u rustshows the process ended with a KILL signal, anddmesgsays "Out of memory". - A SATA SSD or a hard drive
Of the same 127 plans, 44 have a regular SSD and 4 a hard drive. On a slow disk every world save freezes the game. The Palworld documentation warns outright that slow storage can corrupt save data.
How to tell: the description never says NVMe, or the plan name contains "HDD" or "SAS".
- The game needs Windows, but the plan only offers Linux
ARK: Survival Ascended and Enshrouded have no Linux server. You can run them through Proton, but that extra layer breaks with updates, so it is simpler to take a plan with Windows Server from the start.
How to tell: Windows Server is missing from the list of systems at checkout, or the licence is a separate line item. Plans with it are on the Windows VPS page.
- DDoS protection for websites only
All five games take players over UDP, and many filters only understand web traffic. Such a filter will not save a public world on wipe night.
How to tell: the description says "L7 protection" or "website protection". Ask support directly: "do you filter attacks on UDP port 28015?" Plans with protection are on the DDoS-protected VPS page.
Below are the cheapest plans in Russia with 16 GB and four cores, unfiltered by clock or disk. Count the rows with no clock speed; an orange label means the plan has no IP address of its own.
Planning a GTA 5 roleplay server on FiveM? How much memory and CPU it takes and what the launch costs is covered in A GTA 5 RP server after RAGE MP shut down: which VPS FiveM needs.
How to set up a Rust server on Ubuntu
The setup uses Ubuntu 24.04 and Rust, which has an official Linux build. Palworld and Satisfactory install the same way; their app numbers, launch files and ports are noted under the steps. Run commands as root unless noted. A similar guide is in the article on a CS2 server.
- Order the server
Choose Ubuntu 24.04, Moscow or St Petersburg and a plan from the cards above. The game itself takes about 15 GB, and the rest of the disk goes to saves and backups.
- Create a user and install SteamCMD
The game runs without admin rights, so a plugin hole only exposes the game folder. SteamCMD needs the multiverse repository and 32-bit libraries, and the installer will ask you to accept the Steam licence.
apt update && apt -y upgrade add-apt-repository -y multiverse dpkg --add-architecture i386 apt update && apt install -y lib32gcc-s1 steamcmd adduser --disabled-password --gecos "" rust - Download the server
The Rust server's app number is 258550, and you do not need a Steam account to download it. Wait for the line
Success! App '258550' fully installed.su - rust /usr/games/steamcmd +force_install_dir ~/rds +login anonymous +app_update 258550 validate +quit exitPalworld: 2394010, PalServer.sh · Satisfactory: 1690800, FactoryServer.sh
- Open the ports
Players need UDP 28015, the in-game browser needs UDP 28017, and the Rust+ phone app needs TCP 28082. Open the RCON console on TCP 28016 only to your own address, because it gives full control of the server.
ufw allow 22/tcp ufw allow 28015/udp ufw allow 28017/udp ufw allow 28082/tcp # only if you need Rust+ ufw allow from YOUR_IP to any port 28016 proto tcp ufw enablePalworld: 8211/udp · Satisfactory: 7777/udp, 7777/tcp, 8888/tcp
- Turn it into a service
A systemd service restarts Rust after a crash and brings it back after a reboot. A map size of 3500 suits up to 50 people, and the allowed range, per the Facepunch wiki, is 1000 to 6000. Create the file
/etc/systemd/system/rust.serviceand replace the RCON password with your own.[Unit] After=network-online.target Wants=network-online.target [Service] User=rust WorkingDirectory=/home/rust/rds Environment=LD_LIBRARY_PATH=/home/rust/rds/RustDedicated_Data/Plugins/x86_64 ExecStart=/home/rust/rds/RustDedicated -batchmode -nographics +server.port 28015 +server.queryport 28017 +rcon.port 28016 +rcon.password YOUR_PASSWORD +rcon.web 1 +app.port 28082 +server.identity main +server.level "Procedural Map" +server.seed 12345 +server.worldsize 3500 +server.maxplayers 50 +server.hostname "My server" Restart=always RestartSec=10 [Install] WantedBy=multi-user.target - Add a daily restart
An early-morning restart frees the memory picked up during the day, and players barely notice it. For Palworld it is a must.
crontab -e # every day at 6:00 server time 0 6 * * * systemctl restart rust - Start it and connect
The first start builds the map for a few minutes. When the log shows
Server startup complete, open the in-game console with F1 and enter the server address.systemctl daemon-reload systemctl enable --now rust journalctl -u rust -f # in the game console: client.connect SERVER_IP:28015
Wipes. On the first Thursday of the month, stop the service, repeat step 3 to download the update, and start it with a new server.seed so the map is fresh. Oxide plugins also have to be reinstalled after every server update.
Backups. The world and player data live in the ~/rds/server/main folder. Copy it to another machine once a day: a bad plugin can ruin bases people spent three weeks building.
Prices come from hosting companies' websites, converted at the Central Bank of Russia rate. The live blocks refresh hourly and may differ from the text. Minimums and medians were calculated from the accsly.io catalogue on 8 November 2026. All plans for this game are collected on the VPS for Rust page, and there are separate selections for Palworld and for ARK.