How to Set Up a Rust Server in Frankfurt: Complete Guide

Rust is one of the hardest survival games to host well. It eats RAM, punishes slow CPUs, and has a forced monthly wipe that every admin has to plan around. This guide takes you from picking a plan to your first wipe, using a server in Frankfurt, Germany as the example. Frankfurt is the most central location for European Rust communities. YN HOSTING also runs the same Rust plans in Singapore for Asian players, with India and Ashburn (US) coming soon, and every step here works the same in any location.

Why host your Rust server in Frankfurt?

Frankfurt sits on DE-CIX, one of the world's largest internet exchanges. For players in Germany, the Benelux, Austria, Switzerland, Poland, Czechia and Denmark, ping is typically very low. Players in the UK, France, Italy and Scandinavia usually still get a smooth game. If your community is pan-European, Frankfurt is the fairest single choice. It's also where many big EU official and community servers are hosted, so players are used to the latency.

Hosting for Asia instead? Pick Singapore. It's the hub for Southeast Asia, and European servers often mean 150 ms+ ping for players there. YN HOSTING offers the same Rust plans in Singapore (live now; India and Ashburn, US, are coming soon), so you can follow this guide unchanged. Just choose Singapore at checkout and schedule restarts and wipes for SEA quiet hours (around 05:00 SGT).

Step 1: Choose the right amount of RAM

Rust memory use grows with map size, entity count (bases) and plugins, and it climbs over a wipe.

A 4000-size procedural map with a busy population can easily pass 10 GB late in a wipe. Undersizing causes stutter, rubber-banding and crashes during saves.

On YN HOSTING, the Rust plans (Frankfurt and Singapore) are:

New customers on monthly billing can get the first month for $1 by entering the plan's code at checkout. See how the $1 first month works.

CPU matters too

Rust's server simulation leans heavily on single-thread speed. Choose a host that uses high-clock CPUs and NVMe storage. NVMe also shortens world saves, which otherwise cause the familiar save-time hitch.

Step 2: Deploy the server

On a managed host, this takes minutes: 1. Order a Rust plan in the Frankfurt location. 2. Wait for automatic setup. The panel will download the Rust dedicated server files from Steam, which can take a while on first boot. 3. Open the panel and get to know the console, files, startup settings and schedules. Take a tour of your control panel if it's new to you.

If you're self-hosting instead, install SteamCMD and run app_update 258550 validate to download the Rust Dedicated Server.

Step 3: Configure the basics

Rust settings come from startup parameters and server.cfg, found at server/<identity>/cfg/server.cfg.

Key startup parameters

• +server.hostname "Your Server Name | EU | Monthly"
• +server.identity "myserver" (the folder name for your saves)
• +server.level "Procedural Map"
• +server.worldsize 3500
• +server.seed 12345 (choose one at a map preview site before wipe day)
• +server.maxplayers 50
• +server.saveinterval 600

Useful server.cfg lines

server.description "Weekly wipe | Solo/Duo/Trio | EU Frankfurt"
server.url "https://discord.gg/cCUKcyMEuH"
server.headerimage "https://your-image-url/banner.png"
server.tags "monthly,vanilla,eu"

For more, see editing your server config.

Ports

Rust uses a game port (default 28015, UDP), an RCON port (often 28016, TCP) and the Rust+ companion app port (default 28082, TCP). On managed hosting these are assigned for you. Use the ones the panel shows.

Step 4: Set up RCON and admins

Set +rcon.port, +rcon.password "strongpassword" and +rcon.web 1 to manage your server with tools like RustAdmin or the web RCON. To make yourself an owner, run this in the console:

ownerid 7656119XXXXXXXXXX "YourName" "owner"
server.writecfg

Use the live console to run commands without RCON.

Step 5: Add plugins with Oxide (uMod) or Carbon

Most community servers run a modding framework. Oxide/uMod is the long-standing standard, and Carbon is a newer, performance-focused alternative that loads most Oxide plugins. Pick one and don't run both.

Popular starter plugins: - Kits, Better Chat, Remover Tool, NTeleportation, Gather Manager (for 2x/3x servers) - Admin Radar and Vanish for moderation

Install them by dropping .cs files into oxide/plugins/, and they hot-load. Full steps: Rust: install Oxide / uMod plugins.

Tip: Oxide must be updated after every Rust update, including the monthly forced wipe. Until it is, plugins won't load.

Note that adding gameplay-changing plugins (gather rates, kits) makes your server "modded" in the server browser. That's expected, but tag it honestly.

Step 6: Plan your wipe schedule

Facepunch pushes a forced wipe on the first Thursday of every month (around 19:00 UK time). Every server's map is wiped then. Many servers also wipe weekly or bi-weekly in between.

• Map wipe: a new map, and players keep blueprints.
• Full wipe (BP wipe): map and blueprints are both reset.

Announce your schedule in your server description and Discord. Step-by-step instructions are in Rust: how to wipe your server.

Step 7: Keep it fast

• Scheduled restarts: a daily restart at around 05:00 CET clears built-up memory. See set up automatic restarts.
• Entity control: big bases are the main source of late-wipe lag. Use decay and upkeep settings, and plugins that limit entities.
• Save interval: 300–600 seconds is a good balance.
• Right-size the map: a 4500 map with 20 players feels empty and wastes RAM.
• Upgrade if you grow: you can upgrade your RAM without losing the world.

Step 8: Protect against DDoS

Rust servers get attacked, especially around wipe day when competition is highest. Your host's protection matters more than any plugin. YN HOSTING puts every server behind Gcore edge scrubbing and Zero Lag Protection by dataforest. It's always on, at no extra cost, and built to keep play almost lag-free while attacks are filtered. Read how YN HOSTING DDoS protection works.

Step 9: Get players

1. Fill in your hostname, description, header image and tags clearly (wipe schedule, group limits, rates).
2. Share your server address in your Discord.
3. List your server on Rust server-list sites.
4. Run a wipe-day event to get your first population.

FAQ

How much RAM does a Rust server need?

6 GB for small vanilla groups, around 10 GB for typical community servers with plugins, and 16 GB for large or heavily modded ones.

When is the Rust forced wipe?

The first Thursday of every month, when Facepunch releases the monthly update, at around 19:00 UK time.

Oxide or Carbon?

Both work. Oxide has the longest track record. Carbon focuses on performance and loads most Oxide plugins. Choose one.

Is Frankfurt good for UK players?

Generally yes. Ping from the UK to Frankfurt is usually low enough for smooth PvP. Test with your own players.

Can I host a Rust server for Asian players?

Yes. Use a Singapore server for Southeast Asian players. The setup in this guide is identical. India and Ashburn (US) locations are coming soon.

Can I upload a custom map?

Yes. Custom maps need to be hosted at a public download URL and set with +levelurl. Players download it when they join.

How do I stop my server lagging late in a wipe?

Schedule daily restarts, limit entities, keep plugins lean and upgrade RAM if memory stays near your limit.

Start your Rust server

Ready? Pick Frankfurt or Singapore on the Rust server plans and get your first month for $1 with the code entered at checkout. Need help? Join our Discord at https://discord.gg/cCUKcyMEuH.