Rust Server TrendsSeismic network · station log
Recording Stations11,679 Players49,738 Active3,164 Wipes · 3 h118 48 h

Station XX-5899 · recording

Warfare's Rust OctoberWipe

Online 216.73.165.17:28015 checked 10m ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 3
Rank
#5,899
top 27%
Last wipe
26d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-5899 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 10 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+2into Thu 00:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5210:0019:0004:0013:0023:0008:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020010:0019:0004:0013:0023:0008:00

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 27% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 15 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 23:22 UTC26d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
115/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
132/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
184/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
57/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
6/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
24/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Warfare's Rust OctoberWipe?

The procedural map on Warfare's Rust OctoberWipe is size 6,000 with seed 2147483647, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Warfare's Rust OctoberWipe?

The name of Warfare's Rust OctoberWipe gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on Warfare's Rust OctoberWipe?

0 of the 10 slots on Warfare's Rust OctoberWipe are filled right now. Averaged across the last seven days the population was 0 players, reaching a peak of 3. The last 48 hours show their highest activity at 00:00 UTC, averaging 2 players.

How does Warfare's Rust OctoberWipe rank against other Rust servers?

On player hours for the past week, Warfare's Rust OctoberWipe sits at #5,899, which puts it inside the top 27% of every ranked server.

Server details

How reliably does Warfare's Rust OctoberWipe stay online?

Right now, you can reach Warfare's Rust OctoberWipe. Going by the uptime figure it reports, it restarted about 6 days 13 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Does Warfare's Rust OctoberWipe hold a steady tick rate?

The 48-hour average is 108 server fps; 95 is the lowest observed. At its highest, it carried 209,043 entities: buildings, deployables and the world's other contents. It reached a ceiling of 6,094 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does Warfare's Rust OctoberWipe run from?

Nothing about a region comes from Warfare's Rust OctoberWipe. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 216.73.165.17:28015 is the address it uses.

What build of Rust does Warfare's Rust OctoberWipe use?

Rust network protocol 2635 and build 168909 on Windows is what Warfare's Rust OctoberWipe runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on Warfare's Rust OctoberWipe?

The recent wipes averaged a busiest count of 2 players. 15 hours into the latest wipe, the crowd reached its peak.

On what timetable does Warfare's Rust OctoberWipe run its wipes?

The rhythm of Warfare's Rust OctoberWipe cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 26 days 10 hours.

Tags

What do the server tags on Warfare's Rust OctoberWipe mean?

The game's server browser reads the tags Warfare's Rust OctoberWipe publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Warfare's Rust OctoberWipe appear?

The Rust Server Trends lists that take in Warfare's Rust OctoberWipe are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

How do you connect to Warfare's Rust OctoberWipe?

Enter client.connect 216.73.165.17:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp10
Max players Slots: 10.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.