Working its way up from the back of the class: #13,096 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
43/ 100
F
Slipped a little: down 1,960 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
No daily history yet.
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 61% 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
KELQOR WipeGuard QA leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 167.56.171.59:28115.
Is KELQOR WipeGuard QA up, and how steady is its uptime?
The server is down: KELQOR WipeGuard QA is offline now, with the last sighting 14 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 October 2026.
On what Rust version does KELQOR WipeGuard QA sit?
Rust network protocol 2634 and build 167398 on Windows is what KELQOR WipeGuard QA runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does KELQOR WipeGuard QA reset?
The record holds too few of KELQOR WipeGuard QA's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 18 days 8 hours have passed since this world was made.
Population
Where does KELQOR WipeGuard QA place in the wider field of Rust servers?
In the top 61% of all ranked servers, KELQOR WipeGuard QA sits at #13,096 for player hours over the last seven days.
What does the population on KELQOR WipeGuard QA look like?
KELQOR WipeGuard QA is offline at the moment; the last time it was seen was 14 days 6 hours ago.
Tags
What is meant by the tags on KELQOR WipeGuard QA?
gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): Its slot count is 2; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags KELQOR WipeGuard QA publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature KELQOR WipeGuard QA?
These Rust Server Score lists count KELQOR WipeGuard QA among them: Modded Rust 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.
Server rules
Which rules does KELQOR WipeGuard QA enforce, and what are its settings?
The name of KELQOR WipeGuard QA gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is not enabled.
KELQOR WipeGuard QA runs which map?
A procedural map, generated by the game, is what KELQOR WipeGuard QA runs.
Getting in
How do you get onto KELQOR WipeGuard QA?
To connect, start Rust, press F1, and type client.connect 167.56.171.59:28115. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max playersIts slot count is 2.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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. Even marks across the subjects, from F to F.