On the class lists: D (54), with population over 48 hours and no performance mark.
Players now2/ 2001% full
7-day average4peak 11
Rank#1,625top 7%
Last wipe14d agobiweekly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 4 of 200 on average. Plenty of space to grow.
Standingrank on player hours
93/ 100
A
Well up the rankings: #1,625 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: 113 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 130 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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 7% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···F···
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h.
The force wipe · high confidence
usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak21players, last three wipes
crowd held33%else halves by day 3
Coming wipes
7d 6hThu 5 Nov, 19:00 UTCFW
13d 18hThu 12 Nov, 06:35 UTC
27d 18hThu 26 Nov, 06:35 UTC
35d 6hThu 3 Dec, 19:00 UTCFW
41d 18hThu 10 Dec, 06:35 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctThu 24 Sep
Players each hour, from the hour of the wipe. The latest peaked at 19, 9 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 06:35 UTC14d ago
19
–
running
3
Thu 1 Oct, 18:20 UTCFW27d ago
18
halved by day 2
13.5 days
1
Thu 24 Sep, 06:58 UTC35d ago
25
halved by day 4
7.5 days
2
Thu 17 Sep, 07:04 UTC42d ago
22
✓ held half
7 days
0
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
Which region is |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| based in?
You'll find no region listed by |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 46.146.234.109:35100.
How dependable is |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|, and is it online at the moment?
The server is up: |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| is online now. According to its reported uptime, the last restart was about 8 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| perform well?
It never fell below 58 server fps in the last 48 hours, averaging 113. Up to 177,012 entities were in the world, covering buildings, deployables and the rest. Up to 5,557 MB of memory was used. Players feel lag when fps drops and entities pile up.
What Rust version is |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| on?
The server |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| wipe its map?
Its wipe pattern: |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| wipes every other Thursday at 06:35 UTC. 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 14 days 5 hours. Its tags give a wipe schedule of every two weeks.
What happens on |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| when wipe day arrives?
Recent wipes have peaked at 21 players on average. 9 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 33% of its recent wipes. In the other wipes it slipped under half by day 3.
Population
What position does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| hold in the rankings?
Over the last seven days, |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| has #1,625 for player hours, in the top 7% of all ranked servers.
How many players does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| usually have?
With 200 slots available, |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| currently has 2 players. Averaging 4 players over seven days, it peaked at 11. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 9 players.
Tags
What do |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|'s tags stand for?
You'll see |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): 200 slots are available; 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): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): The server wipes on a two-week cycle; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| appear in the Rust Server Score lists and filters?
These Rust Server Score lists count |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| among them: 2x Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 2x.
Rules and settings
Which rules does |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| enforce, and what are its settings?
Going by its name, |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| runs 2x gather. You can play in groups of up to 10 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| uses?
A procedural map of size 4,500 and seed 1337, generated by the game, is what |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots| runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
Getting in
How should you connect to |PVE|S.T.A.L.K.E.R|x2-x4|RaidBase|Event|Kits|Remove|Bots|?
Enter client.connect 46.146.234.109:35100 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://vk.ru/stalkerris.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts10,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max players200 slots are available.
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
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).