On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#5,830top 26%
Last wipe8h agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
74/ 100
B−
Holds a respectable place: #5,830 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 98 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 98 places this week. Nothing a good wipe can't fix.
A term to build on.
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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 26% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·F···
·······
·······
·······
·W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap13.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 11
The first 48 hours of its last wipes
Thu 1 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 19:17 UTC9h ago
–
–
running
0
Thu 1 Oct, 19:51 UTCFW26d ago
2
halved by day 11
26 days
0
Tue 29 Sep, 23:14 UTC28d ago
2
–
1.9 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
No region is published for [QC] WILL 2026 PVE. Rust Server Score takes the server's word for its location and does not trace the hardware. 75.154.161.94:28015 is the address to use.
Is [QC] WILL 2026 PVE up, and how steady is its uptime?
The server is up: [QC] WILL 2026 PVE is online now. The uptime it reports puts the last restart at about 3 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Is [QC] WILL 2026 PVE smooth to play on?
The average over the last 48 hours was 98 server fps, and it never went below 16. At its peak, it held 152,002 entities, including buildings, deployables and all else in the world. Up to 5,360 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is [QC] WILL 2026 PVE running?
Rust network protocol 2635 and build 168909 on Windows is what [QC] WILL 2026 PVE runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [QC] WILL 2026 PVE reset?
[QC] WILL 2026 PVE wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 8 hours.
What happens on [QC] WILL 2026 PVE when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. 4 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 11.
Player count
What position does [QC] WILL 2026 PVE hold in the rankings?
In the top 26% of all ranked servers, [QC] WILL 2026 PVE sits at #5,830 for player hours over the last seven days.
How many players does [QC] WILL 2026 PVE usually have?
[QC] WILL 2026 PVE is showing 0 players right now, with 50 slots in total. It peaked at 2 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 23:00 UTC, averaging 1 players.
Tags
How should you read the tags on [QC] WILL 2026 PVE?
The game's browser takes its cue from the tags [QC] WILL 2026 PVE has set: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [QC] WILL 2026 PVE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [QC] WILL 2026 PVE among them: 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: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Rules and settings
What settings and rules apply on [QC] WILL 2026 PVE?
Nothing in the name of [QC] WILL 2026 PVE states a gather rate. The default of 8 players applies as the group cap. It runs pve, 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.
Which map is in play on [QC] WILL 2026 PVE?
The game generates the procedural map on [QC] WILL 2026 PVE at size 5,000 with seed 753808557. 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.
How to join
What is the way to join [QC] WILL 2026 PVE?
Enter client.connect 75.154.161.94:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^p,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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. Strongest in performance (A+); population is the one to work on (F).