Working its way up from the back of the class: #15,478 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 372 places this week.
A term to build on.
Strongest in momentum (D); standing 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
NA · groups of 30+ · 10x · weekly · 179 on average
136 / 150
Quick answers
from the figures on this page
Server facts
Which region is XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED based in?
XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 75.109.37.163:28016 is the address to use.
How dependable is XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED, and is it online at the moment?
At this moment, XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED is offline; the last time it was seen was 42 days ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
On what Rust version does XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED sit?
Rust network protocol 2633 and build 163794 on Windows is what XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED wipe, and how often?
XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 45 days 7 hours have passed since this world was made.
Population
What position does XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED hold in the rankings?
In the top 70% of all ranked servers, XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED sits at #15,478 for player hours over the last seven days.
Is XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED a busy server?
XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED is offline at the moment; the last time it was seen was 42 days ago.
Tags
What do XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): Its slot count is 150; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): This runs on build 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED?
Rust Server Score lists that include XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED: Rust servers above 10x gather rate, Modded Rust servers, graded and Rust zombie servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: More than 10x.
Map and rules
What settings and rules apply on XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED?
The name of XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED points to a 20x gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED runs which map?
The game generates a procedural map for XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED.
How to join
How do you get onto XESSIVEMINDS PVE X20 ZOMBIES STAY KILL OR BE KILLED?
To connect, start Rust, press F1, and type client.connect 75.109.37.163:28016. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp150
Max playersIts slot count is 150.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 term to build on. Strongest in momentum (D); standing is the one to work on (F).