Server requirements: RAM is everything in Rust
Rust is one of the most memory-hungry games you can host. The official Rust Wiki recommends 12GB of RAM for best performance, and notes that 8GB works fine for small or private servers — testing, building, playing with a few friends. Hostinger states plainly that Rust will not run on Game Panel 1, so 8GB is your floor here, not a budget option. If you are still choosing between games, our game server hosting hub compares all four Game Panel plans side by side.
| Plan | RAM | Honest fit |
|---|---|---|
| Game Panel 1 | 4GB | Not supported — Rust will not run on this plan |
| Game Panel 2 | 8GB | Small private servers: a handful of players, vanilla or light Oxide mods |
| Game Panel 4 | 16GB | Public servers: 50+ players, Oxide plugins, community maps — the sensible default |
| Game Panel 8 | 32GB | Big communities: 100+ slots, heavy mod packs, or Rust plus a second game |
Why so much RAM? Rust’s procedural maps and entity counts scale with your player base and wipe size — a 5k map with hundreds of players eats far more memory than a cozy 2k map with ten friends. The full VPS also runs the OS and Game Panel itself, so don’t size to the bare minimum if you plan to grow. If you’re anywhere between “friends” and “public,” Game Panel 4 is the buy-once-cry-once choice.
How setup works with Game Panel
Rust setup has no token step like CS2 — it’s a straightforward instance creation, and admin access goes through the panel console. The process, verified on Hostinger’s own support guide in October 2026:
- Create the instance. In Game Panel, click Create Instance and select Rust from the application list. The panel handles the server files and base configuration for you.
- Start the server. Launch the instance and give it time to finish its first boot. Rust’s first startup generates the world, so expect it to take a few minutes longer than a CS2 or Minecraft boot.
- Grant yourself admin. Open the server console in Game Panel and type ownerid <your-SteamID> “<your-nickname>”, then writecfg to save it. Use moderatorid <SteamID> “<nickname>” followed by writecfg to add moderators.
- Add Oxide/uMod for plugins. Hostinger’s panel supports Oxide (uMod), the standard Rust modding framework. Install it, drop plugins into the plugins folder, and reload — kits, teleportation, economy, and wipe-protection plugins all work here.
- Connect your players. In Rust, press F1 to open the console and type client.connect <your-server-IP>:28015. The server also appears in the Community and Modded tabs of the in-game server browser once it’s listed.
One Rust-specific habit to build: the game runs monthly forced wipes on the first Thursday of each month. Most communities wipe on the same cadence (often weekly for smaller servers). Schedule your wipes in advance, announce them on your Discord, and use a wipe-protection plugin so the transition doesn’t nuke your players’ goodwill along with their bases.
What it costs
Rust is where Hostinger’s VPS pricing model actually flatters the buyer. Dedicated Rust hosts charge per player slot, and a 100-slot public Rust server on a managed host is not cheap. Hostinger charges per machine — so Game Panel 4 at a VPS-style price can undercut per-slot billing hard once your population grows.
- Game Panel 2 is the minimum buy — it’s the cheapest plan that runs Rust at all, and it’s honest for small private servers.
- Game Panel 4 is the value pick for public servers: 16GB of RAM clears the official 12GB recommendation with headroom for the OS, Oxide, and plugins.
- Watch the renewal. Hostinger’s first-term discounts don’t carry over — renewals bill at the regular price. Rust communities live or die on uptime, so price the renewal, not the intro offer. Full breakdown: Hostinger renewal prices explained.
If your server is truly tiny — three friends, vanilla, 2k map — a per-slot managed host can still win on monthly cost. The moment you add players, mods, or a second server, the full-VPS math takes over.
Hostinger vs dedicated Rust hosts
Dedicated Rust hosts like Shockbyte, Nodecraft, and GameServers specialize in Rust: per-slot pricing, pre-installed Oxide with one-click plugin browsers, and support staff who speak Rust. Hostinger is a generalist VPS with a game panel. Honest comparison:
- Per-slot billing vs per-machine billing: Managed hosts win for small servers (pay for 10 slots, not 16GB of RAM). Hostinger wins as populations grow — a full 16GB box with 60 players costs the same as that box with 10.
- Oxide plugin ecosystem: Dedicated Rust hosts usually bundle one-click Oxide installation and curated plugin lists. On Hostinger you install Oxide yourself through the panel — it’s supported, but it’s a few more clicks.
- Full root access: Hostinger wins. You can tweak server configs directly, run a website or Discord bot on the same box, and spin up a second game (CS2, Minecraft, Valheim) from 100+ templates on the same plan.
- Wipes and maps: Both approaches handle monthly forced wipes. Managed hosts often automate the wipe schedule for you; on Hostinger you configure it yourself, which is more flexible once you know the console.
- Included extras: DDoS protection, NVMe storage, and backups ship with Hostinger’s VPS base at no extra charge. Managed Rust hosts include DDoS too, but off-site backups and extra slots often cost extra.
Verdict: who should and shouldn’t buy
Buy it if: you’re building a real Rust community — public server, Oxide mods, 30–100+ players, maybe a second game or a community website on the same box — and you like full control over configs, wipes, and plugins.
Skip it if: you want the most hand-holding possible for a tiny vanilla server (a per-slot Rust specialist with one-click Oxide is simpler), or your budget genuinely only stretches to a 4GB box — Rust needs 8GB minimum here, no exceptions.
Frequently asked questions
Can I host a Rust server on Hostinger?
Yes. Game Panel includes a one-click Rust template. Note the minimum: Hostinger states Rust will not run on Game Panel 1 — you need Game Panel 2 (8GB RAM) at minimum. Verified on Hostinger’s own support guide (Oct 2026).
How much RAM does a Rust server need?
The official Rust Wiki recommends 12GB for best performance; 8GB works fine for small or private servers. That maps cleanly to Hostinger’s plans: Game Panel 2 (8GB) for small private servers, Game Panel 4 (16GB) for public servers with mods.
Does Hostinger support Oxide/uMod plugins?
Yes. The Game Panel supports Oxide (uMod), Rust’s standard modding framework. Install it, add plugins, and manage them through the panel — kits, teleport, economy, and admin tools all work.
How do I give myself admin on a Hostinger Rust server?
In the Game Panel console, type ownerid <your-SteamID> “<your-nickname>” and then writecfg to save. Add moderators the same way with moderatorid.
How do players connect to my Rust server?
Press F1 in Rust to open the console, then type client.connect <your-server-IP>:28015. Once listed, the server also shows up under the Community and Modded tabs in the in-game browser.
What about Rust’s monthly forced wipes?
Rust force-wipes on the first Thursday of every month. Schedule your wipes around that cadence (many communities also wipe weekly), announce dates on Discord, and consider a wipe-protection plugin so players don’t log in to a surprise.
Related
- Hostinger game server hosting hub — all Game Panel plans and supported games
- Hostinger CS2 server hosting — the shooter alternative on the same Game Panel
- Hostinger Minecraft server hosting — the classic multi-player staple
- Hostinger coupon code — current discounts on game hosting plans
Ready to build your Rust community? Get Game Panel hosting and pick the Rust template at instance creation.
Essential Oxide plugins: what to install first
Oxide (uMod) transforms a vanilla Rust server into a community server. These are the plugin categories to prioritize, in installation order:
- Administration essentials: plugins for improved ban management, player notes, and admin radar. You need visibility into what players are doing before you need gameplay modifications. Install admin tooling first.
- Wipe protection and timing: plugins that manage the wipe cycle: countdown announcements, blueprint wipe vs full wipe configuration, and grace period protection for new players after a wipe. Wipe management is the operational backbone of a Rust community.
- Quality-of-life: stack size modifiers, quick smelt, and craft time reducers. These reduce tedium without breaking game balance. Configure conservatively at first; you can always increase rates, but decreasing them after players are accustomed causes complaints.
- Teleportation and homes: /home and /tpr systems. These are expected on most community servers and their absence is a common reason players leave for other servers. Set reasonable cooldowns and limits to prevent abuse.
- Economy: shop plugins, reward systems for playtime or kills, and trade interfaces. An economy gives players goals beyond raiding. Start simple: a basic shop and playtime rewards. Complex economies require active balancing.
- Anti-cheat supplementation: plugins that detect suspicious behavior patterns (impossible aim statistics, speed anomalies). These complement but do not replace active admin monitoring.
Install plugins one at a time and test each before adding the next. Plugin conflicts are the most common cause of server instability, and isolating which plugin broke something is far easier when you know exactly what changed.
Wipe scheduling and map selection strategy
Wipe cadence defines your server's identity. Choose deliberately:
| Wipe frequency | Map size | Suits |
|---|---|---|
| Weekly | 2k-3k | High-action PvP communities; players who want constant fresh starts |
| Bi-weekly | 3k-3.5k | Balanced communities; enough time to build, frequent enough to stay fresh |
| Monthly (forced wipe aligned) | 3.5k-4.5k | Building-focused groups; large projects need time |
| No wipe (long-term) | 4k+ | Roleplay or PvE communities; requires active entity management |
Map selection: procedural maps are the default and work well. Custom maps (from community creators) offer curated experiences but require downloading and testing. Always test a custom map on a private instance before deploying to production. A broken custom map on wipe day is a community-killing event.
Announce wipes clearly: post the wipe schedule on Discord, in the server description, and via in-game announcements starting 72 hours before. Players who lose progress to a surprise wipe do not return. The wipe-protection plugins mentioned above automate much of this communication.
Performance tuning for high-population servers
When player counts climb past 50, these optimizations matter:
- Entity management: Rust tracks every deployed item, corpse, and dropped object. Set entity cleanup timers aggressively. Abandoned bases with thousands of entities are the primary cause of high-pop lag. Consider a plugin that automatically removes entities from inactive players' bases.
- Tick rate: the default server tick rate is adequate for most populations. Do not increase it hoping for better performance; higher tick rates increase CPU load. If the server struggles, the answer is usually fewer entities, not more ticks.
- AI density: NPCs (scientists, animals, Bradley) consume significant server resources. On high-pop servers, reduce AI spawn rates moderately. Players rarely notice the difference, but the server does.
- Network rate limiting: configure per-player network limits to prevent a single client with a bad connection from consuming disproportionate server resources. This is especially important on public servers.
- RAM headroom monitoring: on Game Panel 4, watch RAM usage during peak hours. If it consistently exceeds 14 GB, you are approaching the limit. Game Panel 8 exists for this reason. Do not wait for out-of-memory crashes to upgrade.
Anti-cheat and admin best practices
Rust's cheating problem is real. Your defenses, in order of effectiveness:
- Active admins beat all plugins. No automated system catches every cheater. Having admins online during peak hours, investigating reports promptly, and banning decisively is the single most effective anti-cheat measure.
- Require Steam accounts in good standing. Configure the server to reject accounts with VAC bans, limited profiles, or very low hours. This does not stop dedicated cheaters (they buy new accounts) but filters casual ones.
- Player reporting system. Make it easy for players to report suspicious behavior: a Discord channel, an in-game command, or both. Respond to reports visibly. A community that sees cheaters banned promptly trusts the server.
- Demo recording. When investigating, record demos of suspected cheaters before banning. This protects against false positives and provides evidence if the ban is disputed.
- Ban escalation: first offense for minor infractions (griefing, toxicity) might be a temporary ban. Cheating (aimbot, ESP, speed hacks) should be permanent on the first confirmed offense. Publish this policy so expectations are clear.
For the shooter alternative on the same Game Panel, see our CS2 server hosting guide.