On the class lists: D (53), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#7,097top 32% · #1091 in NA
Last wipe27d agomonthly schedule
Next wipe7d 18hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
68/ 100
C+
Working its way up from the back of the class: #7,097 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
9/ 100
F
Needs to work on its frame rate: 5 server fps on average.
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 200 places this week.
A term to build on.
Strongest in uptime (A); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 32% of all ranked servers, top 59% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h.
The force wipe · high confidence
wipe-day peak2players, last three wipes
Coming wipes
7d 18hThu 5 Nov, 19:00 UTCFW
35d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 12 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:10 UTCFW27d ago
2
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does We Do Not Eat Our Allies sit?
You'll see We Do Not Eat Our Allies listed in North America, tagged NA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 66.51.98.58:28040 is the address to use.
How reliable is We Do Not Eat Our Allies, and is it up?
You can join now: We Do Not Eat Our Allies is online. About 4 hours ago, it restarted, based on the uptime it reports. It was up 86% of the time over the last 7 full days, 144 of 168 hours. It was first seen by Rust Server Score on 1 October 2026.
How well does We Do Not Eat Our Allies run?
It never fell below 5 server fps in the last 48 hours, averaging 5. Buildings, deployables and everything else in the world added up to as many as 63,684 entities. Up to 2,176 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does We Do Not Eat Our Allies sit?
Rust network protocol 2635 and build 168909 on Linux is what We Do Not Eat Our Allies runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does We Do Not Eat Our Allies wipe its map?
Once a month, We Do Not Eat Our Allies wipes with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 27 days 6 hours have passed since this world was made. The tags show a monthly wipe schedule.
What happens on We Do Not Eat Our Allies when wipe day arrives?
The average peak on its recent wipes was 2 players. 12 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does We Do Not Eat Our Allies place in the wider field of Rust servers?
In North America, We Do Not Eat Our Allies is #1,091, and overall it is #7,097 on player hours over the last seven days, in the top 32% of all ranked servers.
What does the population on We Do Not Eat Our Allies look like?
With 50 slots available, We Do Not Eat Our Allies currently has 0 players. The seven-day average is 0 players, with a peak of 2. Over the last 48 hours, the peak hour was 11:00 UTC, averaging 1 players.
Lists and filters
What do We Do Not Eat Our Allies's tags stand for?
The game's browser takes its cue from the tags We Do Not Eat Our Allies has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it 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 lists and filters on Rust Server Score show We Do Not Eat Our Allies?
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
How is We Do Not Eat Our Allies set up, and what rules does it keep?
The name of We Do Not Eat Our Allies gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
We Do Not Eat Our Allies runs which map?
We Do Not Eat Our Allies runs a game-generated procedural map at size 3,300, seed 270523416. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to We Do Not Eat Our Allies?
Enter client.connect 66.51.98.58:28040 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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 uptime (A); population is the one to work on (F).