Online NA 104.128.58.135:28015 checked 9m ago
Wolvezbane Gaming PVE
Connect
srv = rust.server("104.128.58.135:28016")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 30% of all ranked servers, top 57% in NA. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 27 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:22 UTC FW27d ago | 3 | NaN | running | 0 |
| 1 | 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.
display(srv.map, srv.info())Map
4096 · seed 1
- map
- Procedural Map
- size
- 4096
- seed
- 1
Server
srv.info()- address
- 104.128.58.135:28015
- region
- NA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:22 UTC
- hostname
- –
- first seen
- 19 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Friendly Seattle: No KOS | Chill | Noob Friendly | NA · groups of 8+ · biweekly · 40 on average | 42/100 |
| 1 | [US] Enardo - Random Farming - Small One Grid | OneGrid | NA · groups of 8+ · 28 on average | 40/50 |
| 2 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 26 on average | 7/100 |
| 3 | [NA] Willjum's Casual Solo/Duo Monthly | NA · groups of 8+ · monthly · 15 on average | 13/175 |
| 4 | Rust Degens - US Vanilla | Fridays | NA · groups of 8+ · weekly · 15 on average | 10/150 |
| 5 | Hempville 420 No Kos Low Decay / Limited PvP | NA · groups of 8+ · monthly · 7 on average | 9/90 |
Quick answers
From the figures on this page.
Player counts
What position does Wolvezbane Gaming PVE take in the server rankings?
On seven-day player hours Wolvezbane Gaming PVE is #6,731 overall and #1,052 in North America, inside the top 30% of all ranked servers.
How many players does Wolvezbane Gaming PVE hold at once?
Wolvezbane Gaming PVE reports 1 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 02:00 UTC, averaging 1 players.
Server facts
What does performance look like on Wolvezbane Gaming PVE?
Server fps over the last 48 hours averages 169; the floor is 103. Buildings, deployables and all else in the world took the count as high as 108,322 entities. A high of 3,416 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What Rust version does Wolvezbane Gaming PVE run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Wolvezbane Gaming PVE. The protocol has to match before you can join, and Steam does the updating.
Is Wolvezbane Gaming PVE up, and what does its uptime show?
Online is the state at the latest refresh for Wolvezbane Gaming PVE. A restart about 11 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 19 September 2026.
Where does Wolvezbane Gaming PVE sit?
With its NA tag, Wolvezbane Gaming PVE lists itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. 104.128.58.135:28015 is its address.
Rules, settings, map
Which rules apply on Wolvezbane Gaming PVE, and what settings?
You will not find a gather rate in the string Wolvezbane Gaming PVE. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Wolvezbane Gaming PVE?
The game generates the map on Wolvezbane Gaming PVE: procedural, size 4,096, seed 1. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does Wolvezbane Gaming PVE wipe?
Too few wipes are on record for Wolvezbane Gaming PVE to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 27 days ago.
On Wolvezbane Gaming PVE, what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 27 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 8.
Tags and filters
Where does Wolvezbane Gaming PVE appear among Rust Data lists and filters?
On Rust Data, Wolvezbane Gaming PVE appears in these lists: Modded Rust servers and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Wolvezbane Gaming PVE?
These tags are published by Wolvezbane Gaming PVE and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; NA (North America): North America is its listing in the server browser; oxidation (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Wolvezbane Gaming PVE?
Enter client.connect 104.128.58.135:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fgroups%2F610444460749136 is the website recorded for it.