StatusLive Servers online11,612 Players35,778 Populated2,872 Wiped · 3 h60 Interval5 min Date28 OCT 2026

DWG RG-S5829Server sheetchecked 4m ago

[QC] WILL 2026 PVE

Online 75.154.161.94:28015 checked 4m ago

moddedoxidepve
Connect
Players now 0/ 50 0% full
7-day average0peak 2
Rank#5,829top 26%
Last wipe7h agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeakWipe
00.511.5204:0013:0022:0008:0017:0002:00Wiped Tue 27 Oct, 19:17 UTCWIPE

Hourly average and peak, UTC.

Fig. 1Players on [QC] WILL 2026 PVE
Fig. 2

Server performance

Server fpsWipe
05010015020004:0013:0022:0008:0017:0002:00Wiped Tue 27 Oct, 19:17 UTCWIPE

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 26% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

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
00.511.52+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 2, 4 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 19:17 UTC8h ago – – running 0
Thu 1 Oct, 19:51 UTC FW26d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 244 on average
247 / 2000
02
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 235 on average
104 / 2000
03
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 98 on average
117 / 200
04
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average
41 / 200
05
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 53 on average
11 / 100
06 43 / 250
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is [QC] WILL 2026 PVE online, and what uptime has been recorded?

[QC] WILL 2026 PVE is up at this moment. The uptime it reports puts the last restart at about 2 hours ago. 168 of 168 hours up over the last 7 full days, which is 100% of the time. First seen by Rust Graphs on 13 September 2026.

How does [QC] WILL 2026 PVE perform, as measured?

98 server fps on average over the last 48 hours, and never under 16. Counted at its highest: 152,002 entities, buildings, deployables and the rest of the world included. 5,360 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for [QC] WILL 2026 PVE?

No region is published by [QC] WILL 2026 PVE. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 75.154.161.94:28015.

What Rust version is recorded for [QC] WILL 2026 PVE?

The platform is Windows and the version is Rust network protocol 2635 and build 168909 on [QC] WILL 2026 PVE. The same protocol is required for joining, and Steam updates your game to it.

Population

What player count is recorded on [QC] WILL 2026 PVE?

At the last refresh, [QC] WILL 2026 PVE recorded 0 players across 50 slots. The seven-day mean is 0 players; the peak over the same period is 2. The 48-hour peak falls at 23:00 UTC, averaging 1 players.

What rank has been recorded for [QC] WILL 2026 PVE?

Over the last seven days, [QC] WILL 2026 PVE records #5,829 for player hours: the top 26% of all ranked servers.

Wipe data

What is recorded on [QC] WILL 2026 PVE on wipe day?

The recent wipes averaged a busiest count of 2 players. At 4 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. In the other cases the crowd was below half by day 11.

What wipe schedule has been recorded for [QC] WILL 2026 PVE?

No next wipe can be predicted for [QC] WILL 2026 PVE: its wipes fall at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 7 hours ago.

Settings

Which settings does [QC] WILL 2026 PVE run, and what rules?

No gather rate is stated in the name of [QC] WILL 2026 PVE. No limit is published beyond the default: 8 players per group. It runs the pve game mode, no fighting other players. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

On which map is [QC] WILL 2026 PVE played?

Seed 753808557 and size 5,000 define the procedural map [QC] WILL 2026 PVE generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.

Tags

Where does [QC] WILL 2026 PVE appear among the Rust Graphs lists and filters?

These Rust Graphs lists include [QC] WILL 2026 PVE: Modded Rust servers and PvE Rust servers, plotted. It is returned by these filters on the server list: 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.

On [QC] WILL 2026 PVE, what is meant by each tag?

The game's server browser reads these tags from [QC] WILL 2026 PVE: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^p (PvE): No player combat: the threat comes from the world; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Joining the server

By what method do you join [QC] WILL 2026 PVE?

Connect with client.connect 75.154.161.94:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^p,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players The slot count is 50.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Gameplay

^p
PvE No player combat: the threat comes from the world.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded