Working its way up from the back of the class: #16,408 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 9,096 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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 8d 6h.
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
Which region is We Do Not Eat Our Allies based in?
In North America, according to its own listing, sits We Do Not Eat Our Allies, with the NA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 156.236.84.145:28040 is the address to use.
How reliable is We Do Not Eat Our Allies, and is it up?
At this moment, We Do Not Eat Our Allies is offline; the last time it was seen was 26 days 21 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is We Do Not Eat Our Allies on?
The server We Do Not Eat Our Allies is on Rust network protocol 2633 and build 165217 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does We Do Not Eat Our Allies wipe its map?
The estimate for We Do Not Eat Our Allies'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. 54 days 18 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Population
What position does We Do Not Eat Our Allies hold in the rankings?
Over the last seven days, We Do Not Eat Our Allies has #16,408 for player hours, in the top 69% of all ranked servers and #1,629 in North America.
What does the population on We Do Not Eat Our Allies look like?
It has been 26 days 21 hours since We Do Not Eat Our Allies was last seen, and it is offline right now.
Lists and filters
What do We Do Not Eat Our Allies's tags stand for?
You'll see We Do Not Eat Our Allies tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; NA (North America): The server browser lists it under North America in the browser, which picks them up from the server. 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.
Where does We Do Not Eat Our Allies appear in the Rust Server Score lists and filters?
These Rust Server Score lists count We Do Not Eat Our Allies among them: Modded Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
Which rules does We Do Not Eat Our Allies enforce, and what are its settings?
Nothing in the name of We Do Not Eat Our Allies states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. 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.
We Do Not Eat Our Allies runs which map?
The game generates the procedural map on We Do Not Eat Our Allies at size 3,300 with seed 270523416. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to We Do Not Eat Our Allies?
To connect, start Rust, press F1, and type client.connect 156.236.84.145:28040. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^m,NA,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
NA
North AmericaThe server browser lists it under North America.
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.