Working its way up from the back of the class: #15,218 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
22/ 100
F
Lost ground: down 8,575 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
AveragePeak
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.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
In what location does Dire Wolves | We die the most! sit?
No region is published for Dire Wolves | We die the most!. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 23.17.252.200:28015 is the address to use.
How dependable is Dire Wolves | We die the most!, and is it online at the moment?
At this moment, Dire Wolves | We die the most! is offline; the last time it was seen was 15 days 7 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 11 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Dire Wolves | We die the most! running?
You will find Dire Wolves | We die the most! on Rust network protocol 2634 and build 167584, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Dire Wolves | We die the most! wipe, and how often?
Dire Wolves | We die the most! has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 27 days 22 hours.
Player count
What position does Dire Wolves | We die the most! hold in the rankings?
Over the last seven days, Dire Wolves | We die the most! has #15,218 for player hours, in the top 70% of all ranked servers.
Is Dire Wolves | We die the most! a busy server?
It has been 15 days 7 hours since Dire Wolves | We die the most! was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Dire Wolves | We die the most!?
The game's browser takes its cue from the tags Dire Wolves | We die the most! has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp15 (Max players): Its slot count is 15; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167584 (Build): The game build is 167584; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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 lists and filters on Rust Server Score show Dire Wolves | We die the most!?
These Rust Server Score lists count Dire Wolves | We die the most! among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
How is Dire Wolves | We die the most! set up, and what rules does it keep?
Nothing in the name of Dire Wolves | We die the most! states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Dire Wolves | We die the most!?
The game generates a procedural map for Dire Wolves | We die the most!.
How to join
What is the way to join Dire Wolves | We die the most!?
To connect, start Rust, press F1, and type client.connect 23.17.252.200:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp15,ptrak,$r?,v2634,gmrust,cs167584,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp15
Max playersIts slot count is 15.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167584
BuildThe game build is 167584.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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. Even marks across the subjects, from F to F.