StatusLive Servers online11,611 Players33,784 Populated2,810 Wiped · 3 h69 Interval5 min Date29 OCT 2026

DWG RG-S7001Server sheetchecked 10m ago

Wolvezbane Gaming PVE

Online NA 104.128.58.135:28015 checked 10m ago

moddedoxide
Connect
Players now 0/ 50 0% full
7-day average0peak 2
Rank#7,001top 31% · #1082 in NA
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
00.250.50.75107:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Fig. 1Players on Wolvezbane Gaming PVE
Fig. 2

Server performance

010020030040007:0016:0001:0010:0020:0005: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 19 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 31% of all ranked servers, top 58% in NA. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap12.2 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 8

The first 48 hours of its last wipes

Thu 1 OctSat 19 Sep
01234+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 3, 27 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 22:22 UTC FW27d ago 3 – running 0
Sat 19 Sep, 17:45 UTC39d ago 2 halved by day 8 12.2 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
Friendly Seattle: No KOS | Chill | Noob FriendlyNA · groups of 8+ · biweekly · 41 on average
38 / 100
02 15 / 50
03
[NA] Willjum's Solo Only | Thursday WipesNA · groups of 8+ · weekly · 27 on average
6 / 100
04
Rust Degens - US Vanilla | FridaysNA · groups of 8+ · weekly · 15 on average
1 / 150
05
[NA] Willjum's Casual Solo/Duo MonthlyNA · groups of 8+ · monthly · 15 on average
9 / 175
06
Hempville 420 No Kos Low Decay / Limited PvPNA · groups of 8+ · monthly · 7 on average
7 / 90
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

How reliable is Wolvezbane Gaming PVE, and is it online now?

Right now, Wolvezbane Gaming PVE is recorded as online. Counted from its reported uptime, the last restart was about 19 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 19 September 2026.

What does the recorded performance of Wolvezbane Gaming PVE show?

Average server fps over the last 48 hours is 169; the lowest was 101. Counted at its highest: 108,322 entities, buildings, deployables and the rest of the world included. 3,416 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

In which location is Wolvezbane Gaming PVE hosted?

With its NA tag, Wolvezbane Gaming PVE lists itself in North America. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 104.128.58.135:28015.

On which Rust version is Wolvezbane Gaming PVE running?

On Linux, Wolvezbane Gaming PVE runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.

Counts

What player count is recorded on Wolvezbane Gaming PVE?

At the last refresh, Wolvezbane Gaming PVE recorded 0 players across 50 slots. Averaged across seven days, the player count is 0, with a peak of 2. Over the last 48 hours the busiest hour was 22:00 UTC, at an average of 1 players.

What rank has been recorded for Wolvezbane Gaming PVE?

Across seven days, player hours give Wolvezbane Gaming PVE #7,001 globally and #1,082 in North America, a top 31% position among ranked servers.

Wipe times

On Wolvezbane Gaming PVE, what does the data show for wipe day?

The recent wipes averaged a busiest count of 2 players. 27 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 8.

On Wolvezbane Gaming PVE, when do wipes occur?

Wolvezbane Gaming PVE's rhythm cannot be told yet: too few of its wipes are on record. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 27 days 8 hours ago.

Map and rules

What settings and rules apply on Wolvezbane Gaming PVE?

Gather rate for Wolvezbane Gaming PVE: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

Which map has Wolvezbane Gaming PVE loaded?

Seed 1 and size 4,096 define the procedural map Wolvezbane Gaming PVE generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

Where does Wolvezbane Gaming PVE appear among the Rust Graphs lists and filters?

On Rust Graphs, Wolvezbane Gaming PVE is placed in these lists: Modded Rust servers and Rust server list: North America. It is returned by these filters on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meaning is attached to each tag on Wolvezbane Gaming PVE?

Tags published by Wolvezbane Gaming PVE, and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; NA (North America): The server browser lists it under North America; oxidation (Custom tag): A non-standard tag, set by the owner or a plugin. 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

What is the way to connect to Wolvezbane Gaming PVE?

In Rust, press F1 and type client.connect 104.128.58.135:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fgroups%2F610444460749136.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players The slot count is 50.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Region

NA
North America The server browser lists it under North America.

Other

oxidation
Custom tag A non-standard tag, set by the owner or a plugin.

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