Rust Server TrendsSeismic network · station log
Recording Stations11,690 Players63,224 Active3,459 Wipes · 3 h120 48 h

Station XX-5839 · recording

[QC] WILL 2026 PVE

Online 75.154.161.94:28015 checked 9m ago

moddedoxidepve
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 2
Rank
#5,839
top 26%
Last wipe
15h ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-5839 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Tue 23:00 UTC
Peak · 48 h
2most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.511.5212:0021:0006:0015:0000:0009:00Wiped Tue 27 Oct, 19:17 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
05010015020012:0021:0006:0015:0000:0009: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.

Channel 3 · rank movement

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.

Expected events

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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 27 Oct, 19:17 UTC16h ago – – – – running 0
Thu 1 Oct, 19:51 UTC FW26d ago M0.3rising 2 halved by day 11 26 days 0
Tue 29 Sep, 23:14 UTC28d ago M0.3rising 2 – 1.9 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 246 on average
69/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 236 on average
186/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 100 on average
24/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average
106/ 200
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 52 on average
45/ 100
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 52 on average
28/ 300
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on [QC] WILL 2026 PVE?

[QC] WILL 2026 PVE runs a procedural map of size 5,000 with seed 753808557, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on [QC] WILL 2026 PVE?

The name of [QC] WILL 2026 PVE gives no gather rate. The group limit is 8 players, the game's default. pve is the game mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on [QC] WILL 2026 PVE right now?

A reading taken now shows 0 players on [QC] WILL 2026 PVE, which has 50 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 2. The last 48 hours show their highest activity at 23:00 UTC, averaging 1 players.

How does [QC] WILL 2026 PVE rank against other Rust servers?

The last seven days of player hours place [QC] WILL 2026 PVE at #5,839, in the top 26% of all ranked servers.

Server facts

How reliably does [QC] WILL 2026 PVE stay online?

As recorded now, [QC] WILL 2026 PVE is running. The uptime it reports puts its last restart about 9 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

How well does [QC] WILL 2026 PVE perform under load?

Its average server fps over the last 48 hours was 100, and it never dropped below 16. The world held up to 152,002 entities at its peak, buildings and deployables included. Memory use peaked at 5,360 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does [QC] WILL 2026 PVE run from?

Nothing about a region comes from [QC] WILL 2026 PVE. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 75.154.161.94:28015.

Which Rust version is [QC] WILL 2026 PVE running?

On Windows, [QC] WILL 2026 PVE runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on [QC] WILL 2026 PVE?

On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 4 hours after the wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 11.

How often does [QC] WILL 2026 PVE wipe, and on which days?

No next wipe can be predicted for [QC] WILL 2026 PVE, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 15 hours.

Lists and tags

What do the server tags on [QC] WILL 2026 PVE mean?

The game's server browser reads the tags [QC] WILL 2026 PVE publishes: gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [QC] WILL 2026 PVE appear?

These Rust Server Trends lists include [QC] WILL 2026 PVE: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: 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 to join

How do you connect to [QC] WILL 2026 PVE?

To join, enter client.connect 75.154.161.94:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival in vanilla mode.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.