Rust Server IndexCard catalogue of Rust servers

Holdings11,721 servers56,361 players135 fresh wipes

Call no.5885 On the shelf · online

[QC] WILL 2026 PVE

Online 75.154.161.94:28015 checked 9m ago

Subjects 1. modded2. oxide3. pve
Players now
2/ 50
4% full
7-day average
0
peak 2
Rank
#5,885
top 27%
Last wipeWiped27 OCT2026 · 44m ago
44m ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.250.50.75100:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

05010015020000:0009:0018:0004:0013:0022:00

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Record sheet D · loan terms

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 gap
13.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
0%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

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

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

NA
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 244 on average
322/ 2000
EU
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 234 on average
201/ 2000
NA
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 97 on average
155/ 200
EA
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average
17/ 200
51/ 250
EU
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 53 on average
16/ 100
Reference desk

Quick answers

From the figures on this page.

Rules and settings

What settings and rules does [QC] WILL 2026 PVE run?

No gather rate appears in the name [QC] WILL 2026 PVE. The group limit is 8 players, the game's default. The server runs pve, no combat between players. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map is in use on [QC] WILL 2026 PVE?

Generated by the game, the procedural map of [QC] WILL 2026 PVE has size 6,000 and seed 753808557. You can view the map on RustMaps from this page, as the same size and seed give the same map. The name of the map is Custom Map.

Tags

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

These lists on Rust Server Index take [QC] WILL 2026 PVE: Modded Rust servers, filed by play style and Rust PvE servers, filed A to Z. These filters on the server list bring it up: 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.

How should you read the tags listed for [QC] WILL 2026 PVE?

Filed under these tags, as published by [QC] WILL 2026 PVE and read by the game's server browser: gmvanilla (Game mode): Unmodified survival rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): Build on file: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): A region code is absent; ^p (PvE): Player against player combat is off; the world supplies the danger; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): This one is Modded, since plugins or settings change how it plays. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.

Wipes and resets

What happens on wipe day at [QC] WILL 2026 PVE?

At their busiest, its recent wipes drew 2 players on average. The latest wipe peaked 4 hours in. Its recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the other cases, numbers dropped below half by day 11.

When does [QC] WILL 2026 PVE wipe?

There is no next wipe to predict for [QC] WILL 2026 PVE, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 44 minutes is when its current world was made.

Players and ranking

How is [QC] WILL 2026 PVE ranked compared with the rest?

The seven-day player-hours ranking places [QC] WILL 2026 PVE at #5,885, among the top 27% of ranked servers.

What does the player count on [QC] WILL 2026 PVE look like?

Filed under live counts: [QC] WILL 2026 PVE, 2 players on 50 slots at present. Filed under seven-day figures: an average of 0 players and a peak of 2. Over the last 48 hours, 19:00 UTC drew the highest average: 1 players.

Operator and status

What version does [QC] WILL 2026 PVE use?

Rust network protocol 2635 and build 168909 on Windows is what you will find on [QC] WILL 2026 PVE. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of [QC] WILL 2026 PVE?

You will find [QC] WILL 2026 PVE online as of now. Its reported uptime gives the last restart as roughly 1 hours ago. Uptime for the last 7 full days came to 100%, 168 hours out of 168. It was first recorded by Rust Server Index on 13 September 2026.

How well does [QC] WILL 2026 PVE perform?

The last 48 hours give an average of 99 server fps and a floor of 76. The entity count reached 152,002, covering buildings, deployables and all else in the world. Memory use reached as much as 5,360 MB. A climbing entity count and low fps are felt by players as lag.

Where in the world is [QC] WILL 2026 PVE hosted?

No region is published by [QC] WILL 2026 PVE. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 75.154.161.94:28015.

How to join

What steps lead onto [QC] WILL 2026 PVE?

Enter client.connect 75.154.161.94:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmvanilla
Game mode Unmodified survival rules.
mp50
Max players 50 slots are available.
ts8
Group limit The team limit is 8, as in the standard game.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build Build on file: 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code A region code is absent.

Gameplay

^p
PvE Player against player combat is off; the world supplies the danger.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded This one is Modded, since plugins or settings change how it plays.

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.