[RU] Project Savage PVE X3 | NO RAID | NO KILL
Online 185.207.214.153:35000 checked 8m ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 6% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 14h. The force wipe · high confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 32, 25 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:31 UTC FW27d ago | 32 | – | running | 3 |
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Quick answers
Population
How does [RU] Project Savage PVE X3 | NO RAID | NO KILL rank against other Rust servers?
By player hours over the last seven days, [RU] Project Savage PVE X3 | NO RAID | NO KILL places at #1,272, within the top 6% of ranked servers.
How busy is [RU] Project Savage PVE X3 | NO RAID | NO KILL?
[RU] Project Savage PVE X3 | NO RAID | NO KILL holds 1 players at the moment, out of 200 slots. We counted an average of 6 players in the past week, with 19 at the busiest. The busiest hour in the last 48 was 17:00 UTC, when an average of 12 players were on.
Lists and tags
What do the server tags on [RU] Project Savage PVE X3 | NO RAID | NO KILL mean?
What the game's server browser reads from [RU] Project Savage PVE X3 | NO RAID | NO KILL is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp200 (Max players): The server has 200 slots; ts10 (Group limit): You may team with up to 10 players; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): This server has no region code; ^m (Monthly): Monthly wipes take place, following Facepunch's force wipe; ^p (PvE): Players do not fight each other; the world supplies the danger; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include [RU] Project Savage PVE X3 | NO RAID | NO KILL?
On Rust Population, [RU] Project Savage PVE X3 | NO RAID | NO KILL is filed under these lists: 3x Rust servers, counted live, Rust servers in Europe, Modded Rust servers, counted and PvE servers, counted. These are the filters it appears under when you browse the list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 3x.
Wipe schedule
What does wipe day look like on [RU] Project Savage PVE X3 | NO RAID | NO KILL?
The busiest point of its recent wipes averaged 32 players. 25 hours after the latest wipe the crowd peaked.
What is the wipe schedule on [RU] Project Savage PVE X3 | NO RAID | NO KILL?
Once a month [RU] Project Savage PVE X3 | NO RAID | NO KILL wipes, and that is with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, which takes every Rust server. Counted from 27 days 10 hours ago, that is how long the current world has stood. Its tags give a wipe schedule of one wipe a month.
Map and rules
Which map does [RU] Project Savage PVE X3 | NO RAID | NO KILL run?
A procedural map of size 4,250 from seed 1289664800, generated by the game, is in use on [RU] Project Savage PVE X3 | NO RAID | NO KILL. The map follows from its size and seed, and RustMaps shows it from this page.
What are the rules and settings on [RU] Project Savage PVE X3 | NO RAID | NO KILL?
You gather at 3x on [RU] Project Savage PVE X3 | NO RAID | NO KILL, to judge by the name. The group limit is 10 players. You get pve here, no player combat. Modded is its browser category: plugins or settings change the game. Oxide plugins are in use here. You play with Valve's anti-cheat on: VAC.
About the server
Which version of Rust does [RU] Project Savage PVE X3 | NO RAID | NO KILL run?
On Windows, [RU] Project Savage PVE X3 | NO RAID | NO KILL runs Rust network protocol 2635 and build 168909. Steam updates your game automatically, but you need the same protocol to join.
Does [RU] Project Savage PVE X3 | NO RAID | NO KILL run smoothly?
The last 48 hours saw an average of 87 server fps, with 48 as the lowest. Entities peaked at 247,858, including buildings, deployables and everything else. The highest memory usage was 5,713 MB. Players feel lag when fps is low and the entity count climbs.
Is [RU] Project Savage PVE X3 | NO RAID | NO KILL online, and how reliable is it?
Right now, [RU] Project Savage PVE X3 | NO RAID | NO KILL is online. The uptime it reports suggests a restart roughly 54 minutes ago. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. It was first seen by Rust Population on 13 September 2026.
Where is [RU] Project Savage PVE X3 | NO RAID | NO KILL located?
Nothing in the tags says where [RU] Project Savage PVE X3 | NO RAID | NO KILL is, but its name points to Europe. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 185.207.214.153:35000.
How to join
How do I join [RU] Project Savage PVE X3 | NO RAID | NO KILL?
Open the console with F1 in Rust and enter client.connect 185.207.214.153:35000. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you. You can find its website at https://m.vk.com/projectsavage.