We Do Not Eat Our Allies
Online NA 66.51.98.58:28040 checked 12m ago
Server instruments
last reading Thu 00:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 5 · below 20 is lag, below 10 is badEntities
48 h range 52,330–63,684 · memory 1,702 MBUptime
6 h 0 min since its last restart, at the last readingPlayers
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 32% of all ranked servers, top 59% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 16h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 16hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 16hFW
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 UTC FW27d 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
the same kind of game, then region, group limit, rate and wipes- 26/175
- 7/90
- 3/1000
- 1/15
- 0/50
- 1/50
Quick answers
from the figures on this pageWipe timing
What happens on We Do Not Eat Our Allies when wipe day comes?
An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 12 hours.
What wipe timing does We Do Not Eat Our Allies follow?
The only wipe for We Do Not Eat Our Allies is the force wipe, once a month. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 27 days 8 hours ago. The tags state a wipe schedule of one wipe a month.
Lists and filters
How should you read the tags on We Do Not Eat Our Allies?
Tags published by We Do Not Eat Our Allies, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; NA (North America): Its browser listing: North America. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show We Do Not Eat Our Allies?
Rust Metrics lists featuring We Do Not Eat Our Allies: Modded Rust servers, checked live and North America: server readout. Check: filters. On the server list it appears under these: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Population
What position does We Do Not Eat Our Allies hold among Rust servers?
Player hours over the last seven days put We Do Not Eat Our Allies at #7,105, #1,092 in North America, in the top 32% of all ranked servers.
What player count does We Do Not Eat Our Allies carry?
Current headcount on We Do Not Eat Our Allies: 0 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 2. Check: 48-hour peak. 11:00 UTC, 1 players on average.
Server details
What location is We Do Not Eat Our Allies hosted in?
Its NA tag places We Do Not Eat Our Allies in North America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 66.51.98.58:28040.
What Rust version is We Do Not Eat Our Allies on?
Reading: We Do Not Eat Our Allies, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for We Do Not Eat Our Allies?
Over the last 48 hours the average was 5 server fps; the floor was 5. Reading: 63,684 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,176 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on We Do Not Eat Our Allies, and is it online?
Reading: online. We Do Not Eat Our Allies answers right now. Check: restart. The uptime it reports puts the last restart about 6 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on We Do Not Eat Our Allies?
Reading the name gives no gather rate for We Do Not Eat Our Allies. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
Which map is live on We Do Not Eat Our Allies?
Size 3,300 and seed 270523416: the game generates the procedural map on We Do Not Eat Our Allies from them. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
How can you get onto We Do Not Eat Our Allies?
Press F1 in Rust and enter client.connect 66.51.98.58:28040. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.