Station NA-15490 · no signal
WolfPack Debug
Offline NA 168.100.161.67:30011 checked 41d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,490
- top 69% · #1585 in NA
- Last wipe
- 63d ago
- monthly schedule
- Next wipe
- 6d 20h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on WolfPack Debug?
WolfPack Debug runs a procedural map of size 1,000 with seed 1497489390, 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 WolfPack Debug?
You will find no gather rate in the name of WolfPack Debug. Up to 100 players can be in a group. battlefield is the game mode, kits and high rates for fast PvP. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on WolfPack Debug?
No players are recorded on WolfPack Debug at this moment; it is offline, and the last sighting was 41 days 3 hours ago.
How does WolfPack Debug rank against other Rust servers?
For player hours across the last seven days, WolfPack Debug takes #15,490 overall and #1,585 in North America, inside the top 69% of all ranked servers.
Server details
How reliably does WolfPack Debug stay online?
No contact with WolfPack Debug right now, and the last recorded contact was 41 days 3 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does WolfPack Debug run from?
The NA tag is how WolfPack Debug lists itself in North America. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 168.100.161.67:30011 is the address it uses.
Which Rust version is WolfPack Debug running?
WolfPack Debug is running Rust network protocol 2632 and build 161125 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
How often does WolfPack Debug wipe, and on which days?
From the force wipe the next wipe of WolfPack Debug is estimated. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 63 days 5 hours. A monthly wipe schedule is published in its tags.
Server tags
What do the server tags on WolfPack Debug mean?
The game's server browser reads the tags WolfPack Debug publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts100 (Group limit): Each team can hold up to 100; v2632 (Protocol): Your game needs to be on protocol 2632 to join; cs161125 (Build): Game build: 161125; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^p (PvE): There's no player combat; the world provides the threat; ^i (Battlefield): Kits and high rates drive fast PvP; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; NA (North America): North America is the region it's listed under in the browser. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does WolfPack Debug appear?
These Rust Server Trends lists include WolfPack Debug: Modded Rust servers, tracked live, Rust battlefield servers, Rust PvE servers and North America Rust servers. These filters bring it up on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Connecting
What steps get you onto WolfPack Debug?
You can connect by pressing F1 in Rust and typing client.connect 168.100.161.67:30011 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at https://wolfpack.gg.
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.