On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now3/ 2002% full
7-day average6peak 19
Rank#1,290top 6%
Last wipe27d agomonthly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
3/ 100
F
A quiet classroom so far: 6 of 200 on average. Plenty of space to grow.
Standingrank on player hours
94/ 100
A
Well up the rankings: #1,290 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 88 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 106 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
daily · 1 is best
RankRank in region
Top 6% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h.
The force wipe · high confidence
wipe-day peak32players, last three wipes
Coming wipes
7d 6hThu 5 Nov, 19:00 UTCFW
35d 6hThu 3 Dec, 19:00 UTCFW
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
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:31 UTCFW27d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
EU · groups of 50+ · 3x · biweekly · 30 on average
38 / 100
Quick answers
from the figures on this page
Server facts
Where in the world is [RU] Project Savage PVE X3 | NO RAID | NO KILL?
You won't find a region tag on [RU] Project Savage PVE X3 | NO RAID | NO KILL, but its name indicates Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 185.207.214.153:35000.
How reliable is [RU] Project Savage PVE X3 | NO RAID | NO KILL, and is it up?
The server is up: [RU] Project Savage PVE X3 | NO RAID | NO KILL is online now. The uptime it reports puts the last restart at about 7 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
How well does [RU] Project Savage PVE X3 | NO RAID | NO KILL run?
It averaged 88 server fps over the last 48 hours, with a low of 48. At its peak, it held 247,350 entities, including buildings, deployables and all else in the world. At its highest, it used 5,713 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is [RU] Project Savage PVE X3 | NO RAID | NO KILL on?
You will find [RU] Project Savage PVE X3 | NO RAID | NO KILL on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does [RU] Project Savage PVE X3 | NO RAID | NO KILL wipe its map?
Once a month, [RU] Project Savage PVE X3 | NO RAID | NO KILL wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 27 days 17 hours. Its tags record that it wipes monthly.
What happens on [RU] Project Savage PVE X3 | NO RAID | NO KILL when wipe day arrives?
Across its recent wipes, the busiest moments averaged 32 players. The crowd on the latest wipe was largest 25 hours after it began.
Population
Where does [RU] Project Savage PVE X3 | NO RAID | NO KILL sit among Rust servers?
In the top 6% of all ranked servers, [RU] Project Savage PVE X3 | NO RAID | NO KILL sits at #1,290 for player hours over the last seven days.
What does the population on [RU] Project Savage PVE X3 | NO RAID | NO KILL look like?
[RU] Project Savage PVE X3 | NO RAID | NO KILL is showing 3 players right now, with 200 slots in total. The seven-day average is 6 players, with a peak of 19. The highest average in the last 48 hours came at 17:00 UTC, with 12 players.
Tags and filters
How should you read the tags on [RU] Project Savage PVE X3 | NO RAID | NO KILL?
You'll see [RU] Project Savage PVE X3 | NO RAID | NO KILL tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): Its slot count is 200; ts10 (Group limit): Teams cap out at 10; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does [RU] Project Savage PVE X3 | NO RAID | NO KILL appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [RU] Project Savage PVE X3 | NO RAID | NO KILL among them: 3x Rust servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: 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.
Rules and settings
Which rules does [RU] Project Savage PVE X3 | NO RAID | NO KILL enforce, and what are its settings?
Going by its name, [RU] Project Savage PVE X3 | NO RAID | NO KILL runs 3x gather. The limit for a group is 10 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
[RU] Project Savage PVE X3 | NO RAID | NO KILL runs which map?
The game generates the procedural map on [RU] Project Savage PVE X3 | NO RAID | NO KILL at size 4,250 with seed 1289664800. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join [RU] Project Savage PVE X3 | NO RAID | NO KILL?
Enter client.connect 185.207.214.153:35000 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://m.vk.com/projectsavage.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts10,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max playersIts slot count is 200.
ts10
Group limitTeams cap out at 10.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A steady term. Strongest in performance (A+); population is the one to work on (F).