Working its way up from the back of the class: #15,490 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 360 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Quick answers
from the figures on this page
About the server
Where in the world is WolfPack Debug?
In North America, according to its own listing, sits WolfPack Debug, with the NA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 168.100.161.67:30011.
Is WolfPack Debug up, and how steady is its uptime?
At this moment, WolfPack Debug is offline; the last time it was seen was 40 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does WolfPack Debug sit?
You will find WolfPack Debug on Rust network protocol 2632 and build 161125, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does WolfPack Debug wipe, and how often?
The estimate for WolfPack Debug's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 62 days 14 hours. Its tags record that it wipes monthly.
Population
Where does WolfPack Debug place in the wider field of Rust servers?
Over the last seven days, WolfPack Debug has #15,490 for player hours, in the top 69% of all ranked servers and #1,585 in North America.
What does the population on WolfPack Debug look like?
WolfPack Debug is offline at the moment; the last time it was seen was 40 days 12 hours ago.
Tags
What is meant by the tags on WolfPack Debug?
The game's browser takes its cue from the tags WolfPack Debug has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; ts100 (Group limit): No team may go above 100; v2632 (Protocol): Join only if your game runs protocol 2632; cs161125 (Build): Build number: 161125; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): This is player against world: players do not fight each other; ^i (Battlefield): High rates and kits keep the PvP fast; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): You will find it under North America in the browser. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature WolfPack Debug?
These Rust Server Score lists count WolfPack Debug among them: Modded Rust servers, graded, Rust battlefield servers, graded, Rust PvE servers, graded and North America Rust servers, graded. 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.
Map and rules
How is WolfPack Debug set up, and what rules does it keep?
You will find no gather rate in the name of WolfPack Debug. The limit for a group is 100 players. You get battlefield here, high rates and kits, for fast PvP. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map WolfPack Debug uses?
A procedural map of size 1,000 and seed 1497489390, generated by the game, is what WolfPack Debug runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
Getting in
How do you get onto WolfPack Debug?
To connect, start Rust, press F1, and type client.connect 168.100.161.67:30011. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://wolfpack.gg.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2632,^p,^m,^i,NA,gmrust,cs161125,ts100,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
ts100
Group limitNo team may go above 100.
v2632
ProtocolJoin only if your game runs protocol 2632.
cs161125
BuildBuild number: 161125.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
^i
BattlefieldHigh rates and kits keep the PvP fast.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).