RUST METRICSFlight deck · live data
Data live Servers11,866 Players102,609 Populated3,946 Fresh wipes 3 h551 Scan5 min
‹ All servers75.154.161.94:28015
Offline Full Queue Fresh wipe Wipe due No query

[QC] WILL 2026 PVE

Offline 75.154.161.94:28015 checked 16h ago

moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 03:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 94 SERVER FPS

Server fps

48 h low 16 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 148,971 ×1000

Entities

48 h range 104,899–149,149 · memory 3,729 MB
1239 ET SINCE RESTART 1D 03H

Uptime

1 days 3 hours since its last restart, at the last reading
7-day average0peak 2
Rank#6,360top 29%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory3,729MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5220:0002:0008:0014:0021:0003:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020020:0002:0008:0014:0021:0003: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.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 19:17 UTC2d ago – – running 0
Thu 1 Oct, 19:51 UTC FW28d ago 2 halved by day 11 26 days 0
Tue 29 Sep, 23:14 UTC29d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

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

An average of 2 players came at the busiest on its recent wipes. 4 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 11 when it didn't.

How often does [QC] WILL 2026 PVE wipe, and when?

No next wipe can be predicted for [QC] WILL 2026 PVE, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 47 hours ago.

Lists and filters

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

Tags published by [QC] WILL 2026 PVE, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [QC] WILL 2026 PVE appear in Rust Metrics lists and filters?

Rust Metrics lists featuring [QC] WILL 2026 PVE: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up 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 3 days.

Occupancy

Where does [QC] WILL 2026 PVE sit in the rankings?

Player hours over seven days put [QC] WILL 2026 PVE at #6,360, in the top 29% of all ranked servers.

How full does [QC] WILL 2026 PVE get?

Reading for [QC] WILL 2026 PVE: offline at this moment; last seen 16 hours ago. Check: players over seven days. Average 0, peak 2. Average at the busiest hour was 1 players, at 23:00 UTC over the last 48 hours.

Server details

What location is [QC] WILL 2026 PVE hosted in?

Reading: location. [QC] WILL 2026 PVE gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 75.154.161.94:28015.

What Rust version is [QC] WILL 2026 PVE on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by [QC] WILL 2026 PVE. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on [QC] WILL 2026 PVE within range?

Reading: 107 server fps on average across the last 48 hours. It never dropped below 16. Reading: 149,149 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 4,007 MB. Expect lag when fps falls and entities climb.

What is the uptime on [QC] WILL 2026 PVE, and is it online?

Reading: offline. [QC] WILL 2026 PVE last answered 16 hours ago. By its reported uptime, the last restart was roughly 27 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is [QC] WILL 2026 PVE configured, and what rules are in force?

Check: gather rate. The name [QC] WILL 2026 PVE does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: fighting between players is off. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is [QC] WILL 2026 PVE on?

From seed 753808557, the game generates the procedural map on [QC] WILL 2026 PVE. Its size is 5,000. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name Custom Map.

How to join

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

To join: start Rust, press F1 and type client.connect 75.154.161.94:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.